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 <[EMAIL PROTECTED]> 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 - [EMAIL PROTECTED] Solutions Architect, PORTAL Software Cell: (609) 744-2050 EFax: (617) 344-2585 SMS: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
