Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of rc46fi@googlemail.com
 designates 209.85.218.13 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=EvonXzOYyO4K5o4+ycc3q5xVq+b9qndUdMt/uTcfUCt0oKxXWHGIC4Yr8fXOsP4SMh
         e8sQV+rfMbHvwskslUPoMdpG187JBsXYeUIVVr4CG8SOWSNSFm1vNrE9s8n44R580bAF
         lMSQg9Vb32c3B8H5cdCc9S+qgyp13MBoiEcrc=
Message-ID: <a2d59f0d0812290719v3dab95aak8a52adbdee8f4201@mail.gmail.com>
Date: Mon, 29 Dec 2008 16:19:14 +0100
From: "Gregor Schneider" <rc46fi@googlemail.com>
To: "Tomcat Users List" <users@tomcat.apache.org>
Subject: Re: Optimizing Tomcat with Http11NioProtocol?
In-Reply-To: <21200419.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <21200419.post@talk.nabble.com>

Hi Nodje,

first, the post from Yassine contains some very valuable information.

To me, it looks as if you're fishing in blur waters, since you've got
no idea what might be the bottleneck.

Maybe some additional hints:

- If you're serving quite some of statical content, the Apache
Portable Runtime (APR) might be a good choice:
http://tomcat.apache.org/tomcat-5.5-doc/apr.html

- you might nwat to consider upgrading Tomcat and Java to the latest
version: Java6 had some performance-optimizations, same - if I'm not
mistaken - goes for Tomcat

On Mon, Dec 29, 2008 at 9:57 AM, nodje <nodje.co@gmail.com> wrote:
>
>
> Providing it comes from the Java application side (by the way, any tips on
> how to precisely identify that is more than welcome), and providing that the
> problems come from too many requests, would Http11NioProtocol help Tomcat
> speed up the execution?

If it really comes from your application, you better check the code of
your application first trying to optimize it. Only when you're sure
that your code is clean, proceed to tune Tomcat

> It seems worth trying Http11NioProtocol before going for clustering+load
> balancing. Any advice on the matter?
>

Should be an option, however, bear in mind that you'll have to move to
Tomcat 6 since HttpNio is not available with older versions

> Also we think that request that cannot b served in the reasonable time
> should be refused. Taking into account the described behaviour with the
> default maxThreads=150 and acceptCount =100 values, shouldn't we decrease
> the acceptCount?

Since the default HttpConnector is blocking and your cpu is idleing
and your memory-usage low, I guess you rather should increase the
maxThreads and acceptCount

I suggest you play around with those parameters using JMeter as your
testing-tool. You'll find out pretty fast how those parameters affect
the overall performance

> Tomcat is on a Windows 32bits machine, so even though the machine has 4Gb of
> RAM, the MAX -Xmx size  that we can be used seems to be around 1200Mb. Would
> a 64bits OS automatically allows for more memory usage?

yes

Cheers

Gregor
-- 
just because your paranoid, doesn't mean they're not after you...
gpgp-fp: 79A84FA526807026795E4209D3B3FE028B3170B2
gpgp-key available @ http://pgpkeys.pca.dfn.de:11371

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org