You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2010/02/04 14:48:25 UTC

DO NOT REPLY [Bug 48679] New: performance of getEffectiveLevel can be significantly improved

https://issues.apache.org/bugzilla/show_bug.cgi?id=48679

           Summary: performance of getEffectiveLevel can be significantly
                    improved
           Product: Log4j
           Version: 1.2
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Other
        AssignedTo: log4j-dev@logging.apache.org
        ReportedBy: omry@yadan.net


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.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org