[
https://issues.apache.org/jira/browse/LOG4NET-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner closed LOG4NET-585.
-----------------------------------
Resolution: Information Provided
Assignee: Dominik Psenner
Thanks for reporting this issue. It is sad to hear that with one of the latest
updates to the operating system the performance of the System.Diagnostics
namespace decreases so drastically. However, I don't see anything that we could
do. log4net uses the System.Diagnostics namespace to determine location
information via the StackTrace class. If an update has the performance impact
given, you'll have to file an issue against Microsoft. Alternatively you can
investigate in a workaround yourself. If you find one it would be great if you
could share the insights with the community. Since there's nothing we can do, I
close the issue with resolution "Information Provided".
> log4net became very slow with caller location information after Windows 10
> Fall Creators Update (1709)
> ------------------------------------------------------------------------------------------------------
>
> Key: LOG4NET-585
> URL: https://issues.apache.org/jira/browse/LOG4NET-585
> Project: Log4net
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0.8
> Environment: Windows 10 Pro 64-Bit (1709)
> .NET Framework 4.5.2
> Visual Studio 2015
> Reporter: Tobias Bindel
> Assignee: Dominik Psenner
> Priority: Critical
> Labels: performance, windows
> Attachments: Log4Net.CSharp.zip
>
>
> The documentation of log4net points out that the logging of caller location
> information can be very slow and shouldn't be used unless the performance of
> the software is not affected. And until the Windows 10 Fall Creators Update
> this was the case.
> But after the Windows update (1709) the performance with caller location
> information like %C %M %L is about 100 times slower than without. The
> following results are based on the simple Visual Studio project attached to
> this issue.
> _Results before Windows update (1709)_
> without %C %M %L: Logging of 1000 iterations took: 18 ms.
> with %C %M %L: Logging of 1000 iterations took: 81 ms.
> _Results after Windows update (1709)_
> without %C %M %L: Logging of 1000 iterations took: 14 ms.
> with %C %M %L: Logging of 1000 iterations took: 1502 ms.
> I hope this issue can be fixed or a workaround offered. Thanks in advance!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
