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
ohde-schwarz.com]>
Subject: *EXT* Re: [Newsletter] Re: log4net - performance hit because UserName
is fetched always
Hi Vladimir
That's a very good point - the thread could be impersonating a user
(https://docs.microsoft.com/en-us/dotnet/api/system.security.principal.windowsidentity.getcurrent
[http
ent thread in the mailing list, rather than creating a
> new thread on each response?
>
> Thank you guys
> Denis
>
>
> From: Davyd McColl
> Sent: Tuesday, February 22, 2022 3:29 PM
> To: dev@logging.apache.org
> Cc: Petker Denis 8BM3
> Subject: *EXT* Re: [Newsle
21, 2022 6:43 PM
> > To: dev@logging.apache.org<mailto:dev@logging.apache.org>; Petker Denis
> > 8BM3 <
> > denis.pet...@rohde-schwarz.com<mailto:denis.pet...@rohde-schwarz.com>>
> > Subject: *EXT* [Newsletter] Re: log4net - performance hit because
> UserName
&
e would then be provided to LoggingEvent objects
> > from whatever is creating them?
> >
> >
> > -Original Message-
> > From: Davyd McColl
> > Sent: Monday, February 21, 2022 6:43 PM
> > To: dev@logging.apache.org; Petker Denis 8BM3 <
> &g
ting them?
> >
> >
> > -Original Message-
> > From: Davyd McColl
> > Sent: Monday, February 21, 2022 6:43 PM
> > To: dev@logging.apache.org; Petker Denis 8BM3 <
> > denis.pet...@rohde-schwarz.com>
> > Subject: *EXT* [Newsletter] R
bjects
> from whatever is creating them?
>
>
> -Original Message-
> From: Davyd McColl
> Sent: Monday, February 21, 2022 6:43 PM
> To: dev@logging.apache.org; Petker Denis 8BM3 <
> denis.pet...@rohde-schwarz.com>
> Subject: *EXT* [Newsletter] Re: log4net - perf
, February 21, 2022 6:43 PM
To: dev@logging.apache.org; Petker Denis 8BM3
Subject: *EXT* [Newsletter] Re: log4net - performance hit because UserName is
fetched always
Hi Denis
Thanks for the report (:
I'm happy to review contributions, though for this particular issue, it seems
like
- performance hit because UserName is
fetched always
Hi Denis
Thanks for the report (:
I'm happy to review contributions, though for this particular issue, it seems
like the resolution is to cache the resolved user name, rather than allowing
specifying the name via config. The whole point
