[
https://issues.apache.org/jira/browse/TS-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13247958#comment-13247958
]
Leif Hedstrom commented on TS-1079:
-----------------------------------
I retested too, it's not hugely different, but somewhat noticeable:
{code}
tinkerballa (19:42) 256/0 $ ~/benchit.sh 120 300 100000
http_load -parallel 120 -seconds 300 -keep_alive 100000 /tmp/URL
54287150 fetches on 726 conns, 360 max parallel, 5.428710E+07 bytes, in
300 seconds
1 mean bytes/fetch
180957.1 fetches/sec, 1.809571E+05 bytes/sec
msecs/connect: 0.640 mean, 3.281 max, 0.071 min
msecs/first-response: 1.448 mean, 274.149 max, 0.076 min
tinkerballa (19:55) 260/0 $ ~/benchit.sh 120 300 100000
http_load -parallel 120 -seconds 300 -keep_alive 100000 /tmp/URL
52299871 fetches on 694 conns, 360 max parallel, 5.229990E+07 bytes, in 300
seconds
1 mean bytes/fetch
174332.8 fetches/sec, 1.743328E+05 bytes/sec
msecs/connect: 52.170 mean, 335.854 max, 0.065 min
msecs/first-response: 1.550 mean, 339.591 max, 0.077 min
{code}
The first is current trunk, the second is trunk + 1079. About 3.5% or so,
enough to make me at least curious as to why?
I'm probably ok checking this in if you can't think of anything, but maybe we
need to have a functional configure option for those who really care to
squeeze every ounce out of their system?
> Add an API function to turn debugging on for specific transactions/sessions
> ---------------------------------------------------------------------------
>
> Key: TS-1079
> URL: https://issues.apache.org/jira/browse/TS-1079
> Project: Traffic Server
> Issue Type: Improvement
> Components: Core, HTTP
> Reporter: Uri Shachar
> Assignee: Leif Hedstrom
> Priority: Minor
> Fix For: 3.1.4
>
> Attachments: debug_specific.patch, debug_specific_2.patch,
> debug_specific_3.patch, debug_specific_4.patch
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> When attempting to troubleshoot issues on a production ATS system, it
> is often impossible/difficult to turn on any of the 'high-volume' debug tags
> like http due to the performance impact.
>
> This enhancement allows a plugin to set a debug flag for a specific txn/ssn,
> and replaces some of the internal Debug calls with a new function that checks
> if the flag is turned on, and outputs the debug line regardless of the tag if
> it is (The diags enable/disable flag is still taken into account).
> The API will also have TSDebugSpecific in order to allow plugins to use the
> same functionality.
> In addition, we might consider adding an internal config file (remap-like) to
> allow turning this flag on without plugin intervention.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
