Thanks for the insight.  It looks like we are going to go with server 2003 32
bit.  I found some references that suggest ajp 1.3 has a performance issue in
64 bit server 2008.

-----Original Message-----
From: Tony Anecito [mailto:adanec...@yahoo.com] 
Sent: Monday, February 28, 2011 3:01 PM
To: Tomcat Users List
Subject: Re: IIS7/isapi/tomcat performance

I forgot to mention new versions of Windows are slower than XP. So that would

contribute to your issues. Windows 7 got better but not as fast as 32-bit.

Also, you might want to measure from tomcat perspective so you have a new 
baseline.

Regards,
-Tony



----- Original Message ----
From: Tony Anecito <adanec...@yahoo.com>
To: Tomcat Users List <users@tomcat.apache.org>
Sent: Mon, February 28, 2011 12:57:03 PM
Subject: Re: IIS7/isapi/tomcat performance

Since the memory pointers are larger you may need to increase your heap size
but 

you can compress the address pointers.

Also, if you use JNI and it is 32-bit then you will have unexpected issues
same 
thing with any native libs your try to use.

Generally it will be up to 20% slower due to the pointers.

Recommend you stick to 32-bit if your app fits within the memory space for 
32-bit. I have heard that 64-bit jvm for version 7 might be faster than
32-bit.

Good Luck,
-Tony



----- Original Message ----
From: Tony Anecito <adanec...@yahoo.com>
To: Tomcat Users List <users@tomcat.apache.org>
Sent: Mon, February 28, 2011 12:40:43 PM
Subject: Re: IIS7/isapi/tomcat performance

JVM settings should not be the same.

Regards,
-Tony



----- Original Message ----
From: Bruce Pease <bpe...@wth.com>
To: Tomcat Users List <users@tomcat.apache.org>
Sent: Mon, February 28, 2011 11:46:35 AM
Subject: RE: IIS7/isapi/tomcat performance

Perhaps my point is being missed here.  The issue is moving from 32 bit is
slower in 64 bit (4-500% if you need a number).  Components are the same,
setup is the same, database is the same, environment is the same, tests are
the same, network is the same.  I'm basically looking to see if anyone is
using a similar setup, and has been able to get it to perform well.

-----Original Message-----
From: Tony Anecito [mailto:adanec...@yahoo.com] 
Sent: Monday, February 28, 2011 1:40 PM
To: Tomcat Users List
Subject: Re: IIS7/isapi/tomcat performance

I agree with Charles. I run a performance Testing group for a fortune 50
company 
and do alot of performance testing for different designs/implementation for
my 
own startup and we can not help you without further info.

Client side setup (Browser/version?)
Test cases
Network speed
Tomcat Setup (startup command line with jdk options)
Extending logging options such as request time for tomcat
Make sure your logging is set to error and not debug level on your processes 
(IIS, Tomcat, Database?)

I would use yslow with FF to get page sizes and other info. developers seem
to 
forget that the bandwidth is limited and 1MB pages are too big. Sometimes
images 
are small but the javascript is quite big especially when calling web
services 
directly,
For the middle tier a code profiler like visualvm helps quite a bit.

The key thing is narrow it down tier by tier then focus on the tier where you

see the biggest gains.
If manually you see x seconds then that is the best it will be before you
start 
tuning.
Gains in code will always be larger than that by configuration tuning unless 
logging level is set to high especially for jdbc calls.

Good luck,
Tony Anecito (JavaOne 2010 "I am the future of Java winner")
Founder,
MyUniPortal (JavaOne 2010 "Duke's Award Winner")
http://www.myuniportal.com


 


----- Original Message ----
From: "Caldarale, Charles R" <chuck.caldar...@unisys.com>
To: Tomcat Users List <users@tomcat.apache.org>
Sent: Mon, February 28, 2011 11:15:40 AM
Subject: RE: IIS7/isapi/tomcat performance

> From: Bruce Pease [mailto:bpe...@wth.com] 
> Subject: IIS7/isapi/tomcat performance

> In performance tests I have found the configuration runs
> dramatically slower than it's corresponding server in 32
> bit Windows on 2000 Server and Tomcat 6.

Until you quantify "dramatically", better describe your testing scenario 
(including configurations of all components), eliminate as many moving pieces
as 
you can (e.g., try Tomcat standalone), and do some basic bottleneck analysis,

there's not much anyone can help you with.

- Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


      

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


      

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to