Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 75289 invoked from network); 2 May 2003 06:27:28 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 2 May 2003 06:27:28 -0000 Received: (qmail 22101 invoked by uid 97); 2 May 2003 06:29:38 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@nagoya.betaversion.org Received: (qmail 22094 invoked from network); 2 May 2003 06:29:37 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 2 May 2003 06:29:37 -0000 Received: (qmail 74475 invoked by uid 500); 2 May 2003 06:27:18 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 74464 invoked from network); 2 May 2003 06:27:18 -0000 Received: from icarus.apache.org (208.185.179.13) by daedalus.apache.org with SMTP; 2 May 2003 06:27:18 -0000 Received: (qmail 30784 invoked from network); 2 May 2003 06:27:17 -0000 Received: from unknown (HELO apache.org) (127.0.0.1) by localhost.apache.org with SMTP; 2 May 2003 06:27:17 -0000 Message-ID: <3EB20FCC.6010306@apache.org> Date: Fri, 02 May 2003 08:27:24 +0200 From: Remy Maucherat Organization: ASF User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tomcat Developers List Subject: Re: Tomcat throws 302 errors over load - clustering test References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: localhost.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Filip Hanik wrote: > running the same test with a native C load balancer, the average response > time went from 4.5seconds to 1.9seconds. I don't understand what you really tested, or what you mean by getting 302. 302 is a redirect, why does it indicate an error ? And why would you get more 302s under load ? You had a Java LB in front of the two servers ? Just switching to a native LB improves performance, then ? But does it have any stickiness policy configurable ? Remy >>hi all, >>I recently performed a load test on the clustering solution for >>tomcat 4.1.x >>(http://cvs.apache.org/~fhanik/) >> >>If my unit test is correct, I received 0 replication errors, >>however tomcat >>keeps throwing 302 errors during overload. For those who are >>interested all >>the stats are below, >> >>Even if I run my test against a single tomcat server, I still receive the >>302 errors indicating that this is not a replication error. So in >>case of a >>302 I just resubmit the request once more. >> >>The test WAR and client are available upon request. >> >> >>Setup >>Linux Redhat 7.2, 512MB RAM, 800Mhz P3 >>- 2x Tomcat 4.1.24 (C,D) >>- HTTP Loadbalancer >> >>Win XP Home, 512MB RAM, 2.4GHz P4 >>- 2x Tomcat 4.1.24 (A,B) >>- Replication test client >> >>Network >>- 100Mbs LAN >> >>Test >>- 120 concurrent connections (keep-alive=false) >>- Round robin for each request >>- 100ms between each consecutive request (each connection sleeps >>100ms when >>one request is finished) >> >>Client statistics: >>Thread count=120 >> Average response time=4434ms >> for 600000 requests. >> Nr of replication errors=0 >> Nr of 302 errors=18257 >> >> >>Win XP Statistics (server B): >>[InMemoryReplicationManager] Replication Statistics >> Messages sent=116292 >> Message serialization time=94067ms >> Average serialization time=0.80888623ms >> Average session send size=1808.64bytes >> Messages received=465114 >> Message deserialization time=1816989 >> Average deserialization time=3.9065454ms >> >>Linux Statistics (Server D): >>[InMemoryReplicationManager] Replication Statistics >> Messages sent=232578 >> Message serialization time=625110ms >> Average serialization time=2.6877434ms >> Average session send size=1803.0104bytes >> Messages received=348859 >> Message deserialization time=4482228ms >> Average deserialization time=12.848251ms >> >> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org >>For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org >> >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org > > > --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org