Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 69710 invoked from network); 14 Dec 2008 02:16:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Dec 2008 02:16:16 -0000 Received: (qmail 52138 invoked by uid 500); 14 Dec 2008 02:16:16 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 52114 invoked by uid 500); 14 Dec 2008 02:16:16 -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 52103 invoked by uid 99); 14 Dec 2008 02:16:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Dec 2008 18:16:16 -0800 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Dec 2008 02:15:55 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LBgW5-0005v8-H5 for users@tomcat.apache.org; Sat, 13 Dec 2008 18:15:33 -0800 Message-ID: <20996642.post@talk.nabble.com> Date: Sat, 13 Dec 2008 18:15:33 -0800 (PST) From: kazukin6 To: users@tomcat.apache.org Subject: tomcat6, bottleneck, concurrent requests, windows xp MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: coolwhiff@mail.ru X-Virus-Checked: Checked by ClamAV on apache.org --------------------- 1) there is maxThreads=100 in context.xml 2) sending 100 simultaneous requests to one servlet, for example ab.exe -n 100 -c 100 {address} 3) in the servlet's own log for performance it shows around only 200-500 ms per request 4) in the ab.exe log it shows around 7 seconds(!) per request --------------------- So the question is- is it a some sort of socket level bottleneck? In JProfiler there is no thread locks shown. How to resolve it? ==================================================== full log of ab.exe is ==================================================== Concurrency Level: 100 Time taken for tests: 16.656 seconds Complete requests: 100 Failed requests: 0 Write errors: 0 Total transferred: 2770200 bytes HTML transferred: 2742700 bytes Requests per second: 6.00 [#/sec] (mean) Time per request: 16656.250 [ms] (mean) Time per request: 166.563 [ms] (mean, across all concurrent requests) Transfer rate: 162.42 [Kbytes/sec] received Connection Times (ms) min mean[+/-sd] median max Connect: 31 146 208.0 109 1922 Processing: 1328 8015 4329.2 7797 16250 Waiting: 578 7109 4323.0 6734 15281 Total: 1438 8161 4350.1 7875 16281 Percentage of the requests served within a certain time (ms) 50% 7875 66% 9969 75% 10969 80% 11609 90% 15547 95% 16141 98% 16219 99% 16281 100% 16281 (longest request) -- View this message in context: http://www.nabble.com/tomcat6%2C-bottleneck%2C-concurrent-requests%2C-windows-xp-tp20996642p20996642.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org