Return-Path: Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 1183 invoked from network); 1 Feb 2001 23:02:43 -0000 Received: from unknown (HELO georgia.rubysolutions.com) (root@206.168.42.32) by h31.sny.collab.net with SMTP; 1 Feb 2001 23:02:43 -0000 Received: from rubysolutions.com (IDENT:root@localhost [127.0.0.1]) by georgia.rubysolutions.com (8.9.3/8.8.7) with ESMTP id QAA10359 for ; Thu, 1 Feb 2001 16:02:36 -0700 Message-ID: <3A79EC5F.EA1BE4@rubysolutions.com> Date: Thu, 01 Feb 2001 16:08:15 -0700 From: Steve Ruby Organization: RubySolutions X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en-US,en,en-GB,es MIME-Version: 1.0 To: tomcat-user@jakarta.apache.org Subject: Re: performance References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N That math didn't really work with JMeter anyway... even if you did have 20 threads with 1ms delay, you don't get 20,000 request/sec. Jmeter starts up 20 threads which each make a GET request to the server but each thread only makes another request after it receives an answer then it waits 1ms or 100ms whatever you have it sent to... So if none of the threads get an ansewr then you have 0 requests/sec after they are all tied up. RBinion@lavastorm.com wrote: > > Sorry, that was a typo. Jmeter is configured with a 100 ms delay, 20 threads > :) , although the story is pretty much the same even with a 1000 ms delay. > > ( p.s. I also added an extra couple of fingers to the server so it could > count higher ;) ) > > Bob > > -----Original Message----- > From: Randy Layman [mailto:randy.layman@aswethink.com] > Sent: Thursday, February 01, 2001 3:50 PM > To: tomcat-user@jakarta.apache.org > Subject: RE: performance > > Light load? It looks to me that you are sending > 1ms * 1000 ms/s * 20 threads = 20,000 requests per second to the > server. This would translate to 20K request/second * 60 seconds/min * 60 > minutes/hour = 72,000,000 request per hour. Maybe I'm not understanding the > numbers you quote (I'm not familary with JMeter), but I would be suprised if > any non-clustered web server running on Intel hardware could handle 72 > million hits per hour. > > (Although I would also be suprised if a Microsoft operating system > could count to 72 million ;) ) > > Randy > > -----Original Message----- > From: RBinion@lavastorm.com [mailto:RBinion@lavastorm.com] > Sent: Thursday, February 01, 2001 4:12 PM > To: tomcat-user@jakarta.apache.org > Subject: performance > > Hi, > > I know that Tomcat does not claim to strive for the performance > characteristics of other servlet containers, such as resin. However, I am > wondering just how bad the performance is. I have run some tests, and I have > been a bit surprised. > > Test environment is a 4 proc NT server with 1 gig of memory. I am using > tomcat 3.2.1 running standalone, and have set the max heap size for the JVM > to be about half of physical memory, also I have the server hotspot jit > installed.. Additionally I am using Jmeter to apply some load. > > With 1 Jmeter client configured with a standard delay of 1 ms and 20 > threads, the website being hit becomes essentially non-responsive. Using the > same configuration, but substituting resin for tomcat, shows no noticeable > degradation in performance. > > Again, I am not surprised that resin performs better, but I am surprised > that Tomcat is that much slower, with even a light load applied. > > Are these performance characteristics to be expected. Does these results > surprise anyone. > > Any feedback would be appreciated, and thanks in advance.