hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 20981] - HTTPClient trace() calls a lot of overhead; consider isTraceEnabled() test
Date Mon, 23 Jun 2003 18:41:20 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20981>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20981

HTTPClient trace() calls a lot of overhead; consider isTraceEnabled() test





------- Additional Comments From gojomo@archive.org  2003-06-23 18:41 -------
Short version: updating to commons-logging 1.0.3 fixed the problem

Longer version: I am profiling a web crawling application using the free 
JMechanic profiling plug-in for Eclipse.  Previously with commons logging 
1.0.2, Throwable.getStackTraceElement was taking over 30% of sampled CPU time, 
always triggered by HTTPClient's trace() calls. Now that Jdk14Logger has been 
updated to include the immediate test of logging level (as referred to in 
Adrian's comment), the overhead is negligible. 

Thanks for the comment that highlighted my logging library wasn't doing what 
it should!

Mime
View raw message