You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by Alexey Polyakov <Al...@epam.com> on 2014/06/01 16:49:12 UTC

RE: log4net 1.2.13 performance issues (found the exact line that causes the problem)

Hello,

 

I have encountered a heavy drop in performance after migration from log4net
1.2.10 to 1.2.13. My research pointed out to the commit #1511303 and
specifically to the line 1340:

 
eventProperties[UserNameProperty] = UserName;

 

I attach the test harness I was using - without this line the logging is
done in about 2 seconds, and after this line is added - it takes 24 seconds.

 

Can you please give any comment on what is going on? (is it safe to just
remove this line and use patched version in production environment, or may
be there is already a work in progress and a better solution)/

 

Best Regards,
Alexey Polyakov 
Software Engineer


EPAM Systems
Ryazan office, Russia 
GMT+3 (Standard) / GMT+3 (Daylight)

Office phone:       +7 (4912) 935-733, ext. 46229

Mobile phone:       +7 (910) 509-96-37

E-mail:                  <ma...@epam.com>
Alexey_Polyakov@epam.com

Skype:                  <skype:Aleksey__Polyakov?add> Aleksey__Polyakov (
<skype:Aleksey__Polyakov?chat> chat or  <skype:Aleksey__Polyakov?call> call)

 


RE: log4net 1.2.13 performance issues (found the exact line that causes the problem)

Posted by Alexey Polyakov <Al...@epam.com>.
Sorry, forgot to attach the file.

 

Best Regards,
Alexey Polyakov 
Software Engineer




EPAM Systems
Ryazan office, Russia 
GMT+3 (Standard) / GMT+3 (Daylight)

Office phone:       +7 (4912) 935-733, ext. 46229

Mobile phone:       +7 (910) 509-96-37

E-mail:                  <ma...@epam.com>
Alexey_Polyakov@epam.com

Skype:                  <skype:Aleksey__Polyakov?add> Aleksey__Polyakov (
<skype:Aleksey__Polyakov?chat> chat or  <skype:Aleksey__Polyakov?call> call)

 

From: Alexey Polyakov [mailto:Alexey_Polyakov@epam.com] 
Sent: Sunday, June 01, 2014 6:49 PM
To: log4net-dev@logging.apache.org
Cc: log4net-user@logging.apache.org
Subject: RE: log4net 1.2.13 performance issues (found the exact line that
causes the problem)

 

Hello,

 

I have encountered a heavy drop in performance after migration from log4net
1.2.10 to 1.2.13. My research pointed out to the commit #1511303 and
specifically to the line 1340:

 
eventProperties[UserNameProperty] = UserName;

 

I attach the test harness I was using - without this line the logging is
done in about 2 seconds, and after this line is added - it takes 24 seconds.

 

Can you please give any comment on what is going on? (is it safe to just
remove this line and use patched version in production environment, or may
be there is already a work in progress and a better solution)/

 

Best Regards,
Alexey Polyakov 
Software Engineer


EPAM Systems
Ryazan office, Russia 
GMT+3 (Standard) / GMT+3 (Daylight)

Office phone:       +7 (4912) 935-733, ext. 46229

Mobile phone:       +7 (910) 509-96-37

E-mail:                  <ma...@epam.com>
Alexey_Polyakov@epam.com

Skype:                  <skype:Aleksey__Polyakov?add> Aleksey__Polyakov (
<skype:Aleksey__Polyakov?chat> chat or  <skype:Aleksey__Polyakov?call> call)

 


Re: log4net 1.2.13 performance issues (found the exact line that causes the problem)

Posted by Stefan Bodewig <bo...@apache.org>.
On 2014-06-01, Alexey Polyakov wrote:

> I have encountered a heavy drop in performance after migration from log4net
> 1.2.10 to 1.2.13. My research pointed out to the commit #1511303 and
> specifically to the line 1340:

> eventProperties[UserNameProperty] = UserName;

Seems this is https://issues.apache.org/jira/browse/LOG4NET-429

A possible un-reviewed patch exists, verifying it has been on my TODO
last far too long by now.

Stefan

RE: log4net 1.2.13 performance issues (found the exact line that causes the problem)

Posted by Alexey Polyakov <Al...@epam.com>.
Sorry, forgot to attach the file.

 

Best Regards,
Alexey Polyakov 
Software Engineer




EPAM Systems
Ryazan office, Russia 
GMT+3 (Standard) / GMT+3 (Daylight)

Office phone:       +7 (4912) 935-733, ext. 46229

Mobile phone:       +7 (910) 509-96-37

E-mail:                  <ma...@epam.com>
Alexey_Polyakov@epam.com

Skype:                  <skype:Aleksey__Polyakov?add> Aleksey__Polyakov (
<skype:Aleksey__Polyakov?chat> chat or  <skype:Aleksey__Polyakov?call> call)

 

From: Alexey Polyakov [mailto:Alexey_Polyakov@epam.com] 
Sent: Sunday, June 01, 2014 6:49 PM
To: log4net-dev@logging.apache.org
Cc: log4net-user@logging.apache.org
Subject: RE: log4net 1.2.13 performance issues (found the exact line that
causes the problem)

 

Hello,

 

I have encountered a heavy drop in performance after migration from log4net
1.2.10 to 1.2.13. My research pointed out to the commit #1511303 and
specifically to the line 1340:

 
eventProperties[UserNameProperty] = UserName;

 

I attach the test harness I was using - without this line the logging is
done in about 2 seconds, and after this line is added - it takes 24 seconds.

 

Can you please give any comment on what is going on? (is it safe to just
remove this line and use patched version in production environment, or may
be there is already a work in progress and a better solution)/

 

Best Regards,
Alexey Polyakov 
Software Engineer


EPAM Systems
Ryazan office, Russia 
GMT+3 (Standard) / GMT+3 (Daylight)

Office phone:       +7 (4912) 935-733, ext. 46229

Mobile phone:       +7 (910) 509-96-37

E-mail:                  <ma...@epam.com>
Alexey_Polyakov@epam.com

Skype:                  <skype:Aleksey__Polyakov?add> Aleksey__Polyakov (
<skype:Aleksey__Polyakov?chat> chat or  <skype:Aleksey__Polyakov?call> call)

 


Re: log4net 1.2.13 performance issues (found the exact line that causes the problem)

Posted by Stefan Bodewig <bo...@apache.org>.
On 2014-06-01, Alexey Polyakov wrote:

> I have encountered a heavy drop in performance after migration from log4net
> 1.2.10 to 1.2.13. My research pointed out to the commit #1511303 and
> specifically to the line 1340:

> eventProperties[UserNameProperty] = UserName;

Seems this is https://issues.apache.org/jira/browse/LOG4NET-429

A possible un-reviewed patch exists, verifying it has been on my TODO
last far too long by now.

Stefan