Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 59271 invoked from network); 1 Jun 2007 09:07:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Jun 2007 09:07:23 -0000 Received: (qmail 70246 invoked by uid 500); 1 Jun 2007 08:58:38 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 70078 invoked by uid 500); 1 Jun 2007 08:58:38 -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 70067 invoked by uid 99); 1 Jun 2007 08:58:38 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Jun 2007 01:58:38 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of delbd+jakarta@oma.be designates 193.190.231.71 as permitted sender) Received: from [193.190.231.71] (HELO bonnie.oma.be) (193.190.231.71) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Jun 2007 01:58:33 -0700 Received: from [193.190.249.120] (bonnie.oma.be [193.190.231.71]) by bonnie.oma.be (8.11.1 (Revision 1.5) /8.11.1) with ESMTP id l518wBB04341 for ; Fri, 1 Jun 2007 08:58:11 GMT Message-ID: <465FDFDF.7070301@oma.be> Date: Fri, 01 Jun 2007 10:59:11 +0200 From: David Delbecq User-Agent: Thunderbird 1.5.0.10 (X11/20070403) MIME-Version: 1.0 To: Tomcat Users List Subject: Re: WebApp really slow, Where do I start looking? References: <465FDD74.7020301@omegames.com> In-Reply-To: <465FDD74.7020301@omegames.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Considering CPU usage, it is not 1) a java memory problem, if java memory was full, garbage collector would start using lots of cpu 2) a time consuming java code. It might be one of following 1) synchronized blocks in your code, that would prevent 2 simultaneoous users from doing some operations. 2) use of SingleThreadModel, which has same effect as above 3) Network congestion, you server simply can't send the response to client due to a too small network pipe (80 requests / second resulting each in an about 20k response need a bandwidth of more than 12Mbits) 4) A too small physical memory on system. Eg you configure tomcat to use 1G memory but your server has only 512M available, resulting in memory pagination (swap) and sleeping of java process during pagination process (typically, on unix server, you will see a high % of CPU dedicated to system instead of idle when this happen) One way to test your server performance during heavy is to use apache jmeter. En l'instant pr�cis du 01/06/07 10:48, St�phane Hanser s'exprimait en ces termes: > Hello, > > I've been working on my project for months now, it is my first WebApp > project. Yesterday, I deployed the project on my dedicated server and > a soon as I reached about 80 users, the webapp became really slow. > However, the cpu usage of the server was very low (never more than > 15-20%). I have no idea of what is the cause of this slowness (server > config, bad programming..). > > Can someone help me to diagnostic the problem? Where shoul I start > looking? > > thanks in advance, > > St�phane H. > > > > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org > For additional commands, e-mail: users-help@tomcat.apache.org > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org