RE: Tomcat / WebSphere Performance

2004-02-02 Thread Shapira, Yoav

Howdy,

Tomcat  WAS Win 2K   WAS iSeries
Overall Average Response time  873ms  680ms22206ms

What on earth is this?  How can WAS on an IBM box be 32 times slower
than WAS (same WAS version, same JDK) on a Windows box? ;)

Any comments would be greatly useful.

Find out the intricate details of this test to see if it's applicable to
you at all.  With the above results, I'm doubting the
rigorousness/accuracy of the test.

Yoav Shapira



This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Tomcat / WebSphere Performance

2004-02-02 Thread Tim Funk
There was talk (on this list)  that the IBM JVM on iseries had a massive 
performance bug when a specific log4j attribute was used. (I don't know which 
one)

-Tim

Shapira, Yoav wrote:

Howdy,


  Tomcat  WAS Win 2K   WAS iSeries
Overall Average Response time  873ms  680ms22206ms


What on earth is this?  How can WAS on an IBM box be 32 times slower
than WAS (same WAS version, same JDK) on a Windows box? ;)

Any comments would be greatly useful.


Find out the intricate details of this test to see if it's applicable to
you at all.  With the above results, I'm doubting the
rigorousness/accuracy of the test.
Yoav Shapira



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]