Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 22801 invoked from network); 1 Jun 2009 14:11:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Jun 2009 14:11:00 -0000 Received: (qmail 37685 invoked by uid 500); 1 Jun 2009 14:11:08 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 37653 invoked by uid 500); 1 Jun 2009 14:11:08 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 37642 invoked by uid 99); 1 Jun 2009 14:11:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jun 2009 14:11:08 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [87.194.9.65] (HELO mail.melandra.com) (87.194.9.65) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jun 2009 14:10:58 +0000 Received: from puma.melandra.net ([10.0.0.251]) by puma.melandra.net ([10.0.0.251]) with mapi; Mon, 1 Jun 2009 15:10:37 +0100 From: Peter Crowther To: 'Tomcat Users List' Date: Mon, 1 Jun 2009 15:10:36 +0100 Subject: RE: Tomcat Concurrent Requests Thread-Topic: Tomcat Concurrent Requests Thread-Index: Acniwda+XfRUp+FWQgqSyfjbcOELxQAAEsnA Message-ID: <6715CF65287F8F408DA109EC03AC6C0DBCA5C4C72B@puma.melandra.net> References: <23815501.post@talk.nabble.com> In-Reply-To: <23815501.post@talk.nabble.com> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org > From: CrystalCracker [mailto:sudarshan.acharya@gmail.com] > Given that each request takes 2 seconds on average. Among > them, some of them > take less than 500ms, and some take as long as 5 seconds or > even a little more sometimes. > > How many such concurrent request would a tomcat server > running on a double quad-core server handle? It's totally dependent on your application. If a 5-second request is CPU-b= ound for all that time, very few. If it's mostly waiting for data to be re= turned from a database or web service, probably quite a lot - but you may b= e saturating the database. At the extreme, I could write a webapp that sle= pt for 500ms to 5 seconds, then returned some fixed output - almost no memo= ry use, almost no CPU use, and it would scale very well indeed. There is only one way to find out how your application will perform: measur= e it. And measure end-to-end, with measurements of load-balancers, databas= es, web service back-ends and so on. Anything else won't give you a true p= icture. There is one general point, though. You'll need to set up enough threads o= n your connector that you can handle that degree of concurrency, or Tomcat = will become a bottleneck. - Peter --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org