zh> You could turn off logging altogether in the log4j configuration
zh> and see what happens. There will still be some overhead compared
zh> to removing logging completely, for calls like:
zh> Logger.info(calculateOneMillionDigitsOfPi());
Just one caution ... when you "turn off logging altogeth
lto:[EMAIL PROTECTED]
Sent: Tuesday, February 03, 2004 5:10 AM
To: Log4J Users List
Subject: Re: performance problems IBM JVM
We have no idea what the problem is, someone suggested I try ammending
log4j settings.
We can't remove it totally - it's part of this 3rd party app. All I can
do
In other words, what happens if you remove it?
Robbie
-Original Message-
From: Pete Stokes [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 03, 2004 9:38 AM
To: Log4J Users List
Subject: Re: performance problems IBM JVM
I took out the log4j bits and changed Layout class to SimpleLayo
Are you sure it's log4j which is causing the problem? ;-)
In other words, what happens if you remove it?
Robbie
-Original Message-
From: Pete Stokes [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 03, 2004 9:38 AM
To: Log4J Users List
Subject: Re: performance problems IBM JV
I took out the log4j bits and changed Layout class to SimpleLayout. Even
tried that immediateFlush thing, but to no success! The app on the
iSeries performed *slightly* better, i.e. avg mean time for pages =
25sec rather than 27sec. Tomcat gets sub half second consistently.
I was really hoping
s the
exception the overhead of creation is still incurred.
..then again I could be wrong :)
Tim.
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Log4J Users List" <[EMAIL PROTECTED]>
Sent: Monday, February 02, 2004 10:10 AM
Subject: RE: performance problems IBM JV
Ceki Gülcü <[EMAIL PROTECTED]> wrote on 02/02/2004 12:26:08 PM:
>
> Log4j computes location information by throwing an exception which is
> caught immediately and parsing the stack trace of the exception.
> Apparently, creating an exception on AIX is slower than on other
platforms.
This is a
Log4j computes location information by throwing an exception which is
caught immediately and parsing the stack trace of the exception.
Apparently, creating an exception on AIX is slower than on other platforms.
As throwing exception is not something one does very frequently, the speed
at which
Pete Stokes wrote:
> We have massive performance problems on an app running on iSeries
> WebSphere 4.0.7 (it uses log4j). The app works perfectly on all other
> platforms / servers.
>
> Someone in the Tomcat users list mentioned that there was talk regarding
> a certain log4j attribute when us
