You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "Bryan Call (JIRA)" <ji...@apache.org> on 2016/08/16 22:35:21 UTC

[jira] [Updated] (TS-3571) Should we optimize (defer) the cqu / cquc stringification on logging?

     [ https://issues.apache.org/jira/browse/TS-3571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Call updated TS-3571:
---------------------------
    Assignee:     (was: Meera Mosale Nataraja)

> Should we optimize (defer) the cqu / cquc stringification on logging?
> ---------------------------------------------------------------------
>
>                 Key: TS-3571
>                 URL: https://issues.apache.org/jira/browse/TS-3571
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Logging
>            Reporter: Leif Hedstrom
>             Fix For: sometime
>
>
> Today, we always calculate the strings for cqu and cquc, regardless if they are used or not. This is not optimal, since it's not unusual to use e.g. cquuc instead. In most places where we allow logging URL strings, we also have a way to defer the stringification until we actually need to marshal the URL.
> My suggestion is that we do this deferred string creation for cqu and cquuc as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)