[
https://issues.apache.org/jira/browse/LOG4NET-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16328931#comment-16328931
]
Marc commented on LOG4NET-585:
------------------------------
Sorry, your comment is very clear, I haven't read. Waiting for Microsoft
resolution then...
> 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
(v7.6.3#76005)
