Bug 48679 - performance of getEffectiveLevel can be significantly improved
Summary: performance of getEffectiveLevel can be significantly improved
Status: NEW
Alias: None
Product: Log4j - Now in Jira
Classification: Unclassified
Component: Other (show other bugs)
Version: 1.2
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: log4j-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-04 05:48 UTC by Omry Yadan
Modified: 2010-02-04 05:48 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
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.