Bug 48679

Summary: performance of getEffectiveLevel can be significantly improved
Product: Log4j - Now in Jira Reporter: Omry Yadan <omry>
Component: OtherAssignee: log4j-dev <log4j-dev>
Status: NEW ---    
Severity: normal    
Priority: P2    
Version: 1.2   
Target Milestone: ---   
Hardware: PC   
OS: All   

Description Omry Yadan 2010-02-04 05:48:24 UTC
Whenever the client logs something getEffectiveLevel is called.
getEffectiveLevel in turn, goes up the loggers hierarchy until it finds a logger that have an explicit log level.

it's possible to improve the logging performance by setting the effective level as a member, and maintain it whenever the hierarchy changes or a parent logger level is set.