[LOG4NET-429] Pattern with Context property causes severe slowdown

• Type: Improvement
• Status: Reopened
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.2.13
• Component/s: Core
• Labels: performance
• Assignee: Dominik Psenner
• Reporter: Jonas Versén
• Created: 25/Mar/14 07:17
• Updated: 25/Oct/21 09:56

Description

If you use a context property in your appenders pattern, there will be a significant logging slowdown. In my experience anywhere from 3 to 5 times slower (this will depend on the appender).

I believe that as soon as you use a context property log4net will internally access the windows user name even though it's not the property you want to access. This theory comes from the fact that printing all properties in the pattern (including the costly property username) compared to just printing one will slow down the logging with the same factor.

I've made a stackoverflow question with more details as well

http://stackoverflow.com/questions/22612286/using-log4net-context-properties-has-negative-impact-on-performance/

Issue Links

• duplicates: LOG4NET-421 Inclusion of UserName in composite properties dictionary has a significant performance impact
• is broken by: LOG4NET-205 Allow filtering by Identity / UserName / ThreadName and Domain
• is duplicated by: LOG4NET-533 Log4Net version 1.2.15.0 uses much more CPU than 1.2.11.0
• is related to: LOG4NET-454 Intermittent severe slowdown with RollingFileAppender+MinimalLock
• links to: GitHub Pull Request #5
• links to: GitHub Pull Request #45