Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Users List" <log4j-user@logging.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <44E0C83C.9070502@Stolsvik.com>
Date: Mon, 14 Aug 2006 21:00:12 +0200
From: =?UTF-8?B?RW5kcmUgU3TDuGxzdmlr?= <Endre@Stolsvik.com>
Organization: Home!
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: Log4J Users List <log4j-user@logging.apache.org>
Subject: Re: Log4j 1.2.9, 64-bit, Websphere Performance Problems
References: <5755612.post@talk.nabble.com> <5755664.post@talk.nabble.com>
 <5795740.post@talk.nabble.com> <44E0B1D9.8030408@Stolsvik.com>
 <5801026.post@talk.nabble.com>
In-Reply-To: <5801026.post@talk.nabble.com>
Content-Type: multipart/mixed;
 boundary="------------040009090401020102030808"

--------------040009090401020102030808
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

> If you take a look at my test cases, I did isolate the file I/O.  One of the
> tests writes 1000 statements to the servlet console, which I assume uses
> STDOUT.  That is blazing fast.

Why don't you just try to write some garbage to a file for testing? 
Maybe go to the RollingFileAppender's source and check what it does, and 
try to pinch down what _actually_ is slow - if it is plain 
straigthforward file IO, then you're obviously slightly screwed in 
regards to "pure java" bughunting.

.. and btw, customers that have an aversion to profilers should be shot, 
at least a little bit!

> The file is on a local system, not remote.  There is no J2EE security
> enabled or anything.

> 
> One concerning thing is that even the stand-alone Java application writes
> log statement 4 times slower.

Right..

Again - make a servlet or bean or whatever (standalone java is obviously 
the simplest testing platform here), and just write a megabyte of 
garbage to a file, try both binary (bytestream) and chars (maybe its the 
charset conversion?!), try also in some different locations, just to 
rule out "strange areas" of the filesystem - check the speed against 
your own setup. You could maybe profile the standalone application, at 
least? Even remote; both JProfiler and YourKit (the two I know!) can do 
"profile-to-file" stuff.

Happy hacking!
Regards,
Endre.


--------------040009090401020102030808
Content-Type: text/plain; charset=us-ascii

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
--------------040009090401020102030808--