[
https://issues.apache.org/jira/browse/TS-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14950607#comment-14950607
]
Susan Hinrichs commented on TS-3072:
------------------------------------
Ignore my previous performance numbers. I had some servers missing when I ran
that.
I ran a cache scenario on my 1GB network machine and 4 multi-threaded clients.
The clients fetch a cached 512 byte item. I'm still testing three cases. In
addition to rps changes, I noted the change in CPU % utilization from perf top
for Diags:on and pthread_get_specific.
Base (not including this code change). 163125 rps. .97% in Diags::on and
0.61% in pthread_get_specific
New (enable set to 0). 163169 rps. 1.19% in Diags:on and 0.58% in
pthread_get_specific
New (enable set to 2). 162777 rps. 1.3% Diags::on and 1.06% in
pthread_get_specific
So the impact of enabling the Debug IP checking but not actually matching (and
logging) seems pretty minimal. In these experiments, we spend roughly extra
0.75% CPU and lose roughly 400 rps (or 0.2% reduction).
No real impact in adding the code but leaving debug.enabled at 0.
> 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)
