From: Ciummo, L. <Law...@em...> - 2014-04-02 17:46:15
|
I've got an application that does a lot of disk IO set up to use about 1000 different log files. Normally, the log level is set to DEBUG level so that there is almost no logging at runtime (maybe 2-3 logs over a 4 hour period). I see about a 5% hit to overall performance (measured by IOPS to the disks) when logging code in my build (ie it's 5% faster without any log4cplus code at all ). Is there any explanation for this? Does a call like... LOG4CPLUS_TRACE(_drive_logger, "Entering... debug=" << debug); Cause any processing with log level set to DEBUG? Is the string constructed if the logging level set to DEBUG. Thanks Larry |