tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert F. Hall" <rfh...@berkeley.edu>
Subject Re: [OT] Throughput and scalability
Date Thu, 24 Feb 2005 00:49:01 GMT
Ross,

I recommend that you think along the lines of expandability.
That is, a load balancer in front of tomcat(s) running on one or
more servers.  As demand increases you add more instances,
then another server.  There is also the nature of the communication
with the external system to consider.  It sounds like you should
profile the app at a range of loads, identify bottlenecks, and
design/specify accordingly.

-Robert

Larry Meadors wrote:

>I do not think that anyone can answer that but you. 
>
>It is so application specific that any answers we give would be SWAGs at best.
>
>Larry
>
>
>On Wed, 23 Feb 2005 14:25:32 -0800, Ross Poppel <rpoppel@portal.com> wrote:
>  
>
>>Hi Tomcat Users -
>>We are implementing Tomcat (with Axis) for HTML translation to a
>>proprietary format (as a pass-thru).  This is for submission to an
>>external system (its pretty simple data) and back again.
>>
>>We were wondering if anyone has any ideas how you would size a box
>>(Solaris/HP-UX based) if you want to get a specific throughput (x number
>>of messages per second).  Is there any guidelines anyone can recommend?
>>
>>-----------------------------------------------------------------------
>>Ross Poppel - rpoppel@portal.com
>>Solutions Architect, PORTAL Software
>>Cell:  (609) 744-2050
>>EFax:  (617) 344-2585
>>SMS:   6097442050@mobile.mycingular.com
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>>
>>
>>    
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
>  
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message