Hi Davyd,
I’m not quite sure, whether I fully understood you. Our use-case is pretty
simple: we don’t use impersonating, we don’t log the username and we don’t use
the username for filtering log-events etc. So we are not interested in username
at all. Nevertheless, we are suffering from the slo
Again not sure if this is applicable to your case, there are some
discussions regarding UserName and performance in internet, like this one
(with sql appender specifics)
https://www.codewrecks.com/post/old/2015/03/bufferingappenderskeleton-performance-problem-in-log4net/
As a result they refer to
Hi Vladimir
(to clarify, from here on "fixed" refers to being unchanging, not reverted from
a broken state, and much of this message is for my own benefit as there are
still large portions of log4net that I'm not well-acquainted with)
I believe you're on the right track here - the added propert
for the bad responsivness
From: Davyd McColl
Sent: Wednesday, February 23, 2022 7:51 AM
To: Vladimir Vedeneev ; dev@logging.apache.org
Cc: Petker Denis 8BM3
Subject: *EXT* [Newsletter] Re: Re: [Newsletter] Re: log4net - performance hit
because UserName is fetched always
Hi Vladimir
(to clarify