[
https://issues.apache.org/jira/browse/TS-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948975#comment-14948975
]
Susan Hinrichs commented on TS-3072:
------------------------------------
I ran some tests on my test harness machines. It is configured in proxy mode
(no caching) making GET requests. 1KB objects are exchanged. Three requests
per connection. No SSL. Single 1Gb interface. I ran my clients at not quite
resource exhaustion to measure a steady state performance.
Run cases:
* Base: A build without client_ip debug code. diags.debug enabled = 0
* New0: A build with client_ip debug code. diags.debug enabled = 0
* New2-mismatch: A build with client_ip debug code. diags.debug.enabled = 2
and diags.debug.client_ip = IP address not involved in the test.
I also tried running with an IP matching one of my test clients and http tag
set, the client fell over.
Base and New0 had very similar performance. About 56,600 rps.
New2-mismatch was around 53,900 rps.
So enabling the client_ip even if nothing matches incurs around a 5%
performance penalty. But this is only seen if the configuration is explicitly
set from 0 to 2. In the depths of an investigation, this might be an
acceptable performance penalty.
> Debug logging for a single connection in production traffic.
> ------------------------------------------------------------
>
> Key: TS-3072
> URL: https://issues.apache.org/jira/browse/TS-3072
> Project: Traffic Server
> Issue Type: Improvement
> Components: Core, Logging
> Affects Versions: 5.0.1
> Reporter: Sudheer Vinukonda
> Assignee: Susan Hinrichs
> Labels: Yahoo
> Fix For: sometime
>
> Attachments: ts-3072.diff
>
>
> Presently, when there's a production issue (e.g. TS-3049, TS-2983 etc), it is
> really hard to isolate/debug with the high traffic. Turning on debug logs in
> traffic is unfortunately not an option due to performance impacts. Even if
> you took a performance hit and turned on the logs, it is just as hard to
> separate out the logs for a single connection/transaction among the millions
> of the logs output in a short period of time.
> I think it would be good if there's a way to turn on debug logs in a
> controlled manner in production environment. One simple option is to support
> a config setting for example, with a client-ip, which when set, would turn on
> debug logs for any connection made by just that one client. If needed,
> instead of one client-ip, we may allow configuring up to 'n' (say, 5)
> client-ips.
> If there are other ideas, please comment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
