Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
1.2.13
-
None
-
Issue was observed on Windows Server 2008 R2 with an ASP.NET 4.0 application.
Description
A change made for LOG4NET-205 has the LoggingEvent.CreateCompositeProperties method get the UserName property for every log event. Since getting the UserName is very slow, this change has a significant impact on performance in log4net.
In one trace captured with dotTrace on a large web application we found that the get UserName property (called from CreateCompositeProperties) accounted for 34% of all time spent in log4net code.
Our workaround for the issue has been to "fix" the UserName property by adding <fix value="32" /> to all our appenders.
Attachments
Issue Links
- is duplicated by
-
LOG4NET-429 Pattern with Context property causes severe slowdown
- Reopened
- is related to
-
LOG4NET-454 Intermittent severe slowdown with RollingFileAppender+MinimalLock
- Open