Re: Tomcat scalability

Quoting Jon Scott Stevens <[EMAIL PROTECTED]>: > on 2002/11/3 2:24 PM, "Bojan Smojver" <[EMAIL PROTECTED]> wrote: > > > I know you have a much better machine, but 1600 transactions does seem a > > bit high. > > Not for porn. Nah... they wouldn't use Java for that. They'd use Porn Hypertext Proc

Re: Tomcat scalability

on 2002/11/3 2:24 PM, "Bojan Smojver" <[EMAIL PROTECTED]> wrote: > I know you have a much better machine, but 1600 transactions does seem a > bit high. Not for porn. Ahaha... -jon -- To unsubscribe, e-mail: For additional commands, e-mail:

Re: Tomcat scalability

Although this might be completely meaningless in you situation, I'll post it for orientation anyway. The benchmarks were done on 1 GHz Athlon machine with 1/2 GB RAM and 80 GB IDE disk, running JBoss 2.4.7, Tomcat 3.3.1, Apache 2.0.43, mod_jk 1.2.0 on RedHat Linux 7.3, with IBM JDK 1.3.1 release cx

Re: Tomcat scalability

One good rule of thumb is not to solve problems that don't exist. Your first task is to set up a server and hit it with something a good 20%-50% more demanding than your expected load. There exist several automated tools to do this. One is JMeter at http://jakarta.apache.org/jmeter/index.htm

Re: Tomcat scalability

<[EMAIL PROTECTED]To: [EMAIL PROTECTED] a> cc: Subject: Tomcat scalability

RE: Tomcat scalability

You would be better off to use a load balancer in front of a cluster of Tomcat servers. It gives you very good scalability, with good fault tolerance. -Original Message- From: ryan [mailto:rsburgess@;shaw.ca] Sent: 03 November, 2002 12:39 AM To: [EMAIL PROTECTED] Subject: Tomcat

Tomcat scalability

1. For a project my company is working on we have transactions requirements of 1600 transactions per second. The transactions consists of processing a servlet in Tomcat, doing a database call and then displaying the results to the user so the effective number of transactions Tomcat has to proce