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

Posted to log4net-dev@logging.apache.org by "Tom Voros (JIRA)" <ji...@apache.org> on 2014/02/04 17:08:08 UTC

[jira] [Updated] (LOG4NET-421) Inclusion of UserName in composite properties dictionary has a significant performance impact

     [ https://issues.apache.org/jira/browse/LOG4NET-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Voros updated LOG4NET-421:
------------------------------

    Environment: Issue was observed on Windows Server 2008 R2 with an ASP.NET 4.0 application.  (was: Issue was observed on Windows Server 2008 R2)

> Inclusion of UserName in composite properties dictionary has a significant performance impact
> ---------------------------------------------------------------------------------------------
>
>                 Key: LOG4NET-421
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-421
>             Project: Log4net
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.13
>         Environment: Issue was observed on Windows Server 2008 R2 with an ASP.NET 4.0 application.
>            Reporter: Tom Voros
>              Labels: performance
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)