Thanks Alex.
We've reduced the number of maxThreads on the server and will see what
effect it has. I can certainly see that a large number of concurrent
threads all handling similar requests will probably run slower than
executing those requests sequentially.
Steve
-----Original Message-----
From:
[hidden email] [mailto:
[hidden email]] On Behalf Of
Alessandro Vernet
Sent: 22 February 2006 23:15
To:
[hidden email]
Subject: Re: [ops-users] Tomcat configuration: maxThreads, acceptCount
Hi Stephen,
In most of the cases we have seen so far, a good strategy is to set
the maximum number of "threads" or "processors" to just slightly more
than the number of CPUs you have. This strategy applies broadly to web
applications, not only to PresentationServer. There is a good
discussion about this in the WebLogic Performance and Tuning
documentation:
http://e-docs.bea.com/wls/docs81/perform/WLSTuning.html#1140013Alex
On 2/17/06, Stephen Bayliss <
[hidden email]> wrote:
people's
> experience with tuning Tomcat for running OPS by modifying these
values?
>
>
>
> We're currently still with the defaults (on Tomcat 5.0.28, maxThreads
is
> 150, acceptCount is 100) and we do get situations where the server
seems to
> hang (or at least sits at 100% CPU for some time).
>
>
>
> Steve
>
> --
> You receive this message as a subscriber of the
[hidden email]
> mailing list.
> To unsubscribe: mailto:
[hidden email]
> For general help: mailto:
[hidden email]?subject=help
> ObjectWeb mailing lists service home page:
http://www.objectweb.org/wws>
>
>
--
Blog (XML, Web apps, Open Source):
http://www.orbeon.com/blog/--
You receive this message as a subscriber of the
[hidden email] mailing list.
To unsubscribe: mailto:
[hidden email]
For general help: mailto:
[hidden email]?subject=help
ObjectWeb mailing lists service home page:
http://www.objectweb.org/wws
Locked
