log4net - performance hit because UserName is fetched always

Hi all, we have upgraded the log4net version from 1.2.10 to the newest version 2.0.14 and are now facing performace issues. I already have done some investigation looking at the log4net code. With the ticket LOG4NET-205 a change has been introd

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 the resolution is to cache the resolved user name, rather than allowing specifying the name via config. The whole point of this property is to log the username under which the pr

RE: [Newsletter] Re: log4net - performance hit because UserName is fetched always

er] 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 the resolution is to cache the resolved user name, rather than allowing specifying the name via config

RE: [Newsletter] Re: log4net - performance hit because UserName is fetched always

McColl Sent: Monday, 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

Re: [Newsletter] Re: log4net - performance hit because UserName is fetched always

ed 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 < > denis.pet...@rohde-schwarz.com> > Subject: *EXT* [Newsletter] Re

Re: [Newsletter] Re: log4net - performance hit because UserName is fetched always

gt; > 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> > > Sub

Re: [Newsletter] Re: log4net - performance hit because UserName is fetched always

ggingEvent > class > > I guess. So the username 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@log

RE: [Newsletter] [Newsletter] Re: log4net - performance hit because UserName is fetched always

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<mailto:dev@logging.apache.org>; Petker Denis 8BM3 Subject: *EXT* [Newsletter] Re: log4net - performance hit because User

RE: [Newsletter] [Newsletter] Re: log4net - performance hit because UserName is fetched always

ry 22, 2022 10:22 AM To: dev@logging.apache.org Cc: Petker Denis 8BM3 Subject: *EXT* [Newsletter] RE: [Newsletter] Re: log4net - performance hit because UserName is fetched always Hi Denis I would imagine that the use case is for shared logging config between processes. I think that the iss

RE: Re: [Newsletter] Re: log4net - performance hit because UserName is fetched always

gt; From: Davyd McColl > > Sent: Monday, February 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: Re: [Newsletter] Re: log4net - performance hit because UserName is fetched always

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

Re: Re: [Newsletter] Re: log4net - performance hit because UserName is fetched always

BM3 mailto:denis.pet...@rohde-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.wind

RE: [Newsletter] Re: Re: [Newsletter] Re: log4net - performance hit because UserName is fetched always

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