Thanks Walden for the reply, that makes total sense. The error is on our part
(we're in production with debug on as its a greenfield project).
This second reply to my question brings me to my point. What was actually
happening (and this is speculation), is that my code changes related to
per
What appenders are you using? I assume one of them is the rolling file
appender? How large is the log file produced with the setting at DEBUG vs
INFO?
If you need to keep the debug information you can look at
the BufferingForwardingAppender. The following will buffer 255 messages
before writing t
Graham,
That's not a log4net issue as much as it's an issue in your application.
Sounds like your application (like many) makes lots of log.Debug()
calls, to log, um, debug information. By switching the logging from
DEBUG to INFO you've stopped all those log entries from being written to
disk. Eve
Hi,
I just switch from DEBUG to INFO in our application logging and the
difference is pretty much stunning. E.G. our perf has gone from 23
seconds down to 14 because of the change. Is this a known issue. i.e.
debug log level is expected to impose this kind of overhead.
Thanks
Graham
Ce message
