My app has about 270 simultaneous site connections, each sending data
pretty much continuously (it's instrumentation readings). The total
data readings I receiven averages about 2.1 million per day, and ranges
from about 50 to 500 per second. I run a single instance of tomcat on a
single machine with 600 threads, and tomcat very rarely goes above 15%
cpu usage, averaging about 8-10%. That includes decryption of the
incoming data, error checking, and encryption of the response.


Li Ma wrote:

> Thanks for the suggestions. I agree lots of stuff can only be decided
> after
> putting into a specific environment. But still, any number that can be
> shared?
>
> How many concurrent users your Tomcat can serve?
>
> Thanks again!
>
> Li
>
> On 12/24/06, Gary Evesson <lists@(protected):
>
>>
>> Generally in a production environment, increasing the number of threads
>> from
>> the default is compulsory. You need to balance that against the
>> amount of
>> memory that you have allocated for your JVM, which needs to be balanced
>> against the amount of memory available in the machine.
>>
>> Handling concurrent users generally comes back to the number of
>> connections
>> that your architecture can handle and how much work your database
>> server(s)
>> (assuming you have some) can handle. Our experience has been that these
>> things become an issue before tomcat does. It depends on your
>> application
>> *a
>> lot*.
>>
>> Nothing beats real load testing to figure out where *your* stress points
>> are. They are probably going to be different to other people...
>>
>> Gary
>>
>> -----Original Message-----
>> From: Li Ma [mailto:lima01@(protected)]
>> Sent: Sunday, December 24, 2006 12:35 PM
>> To: Tomcat Users List
>> Subject: Re: Peak load of Tomcat-powered server(s)?
>>
>> Actually you can imagine the server serves a site like mySpace where
>> people
>> can access their own home, blog, images, forum, etc. I know it is still
>> not
>> easy to answer, but I'm not looking for an answer to my specific
>> question.
>> I'm just looking for any similiar experience that can be shared and
>> hoping
>> I
>> can learn some.
>>
>> Another question, how many threads do you think Tomcat can have on one
>> machine? And will increasing number of threads help processing more
>> requests? I think 100-150 per server per second is not a good number.
>> But
>> if
>> it is true, does that mean Tomcat is not suitable for large website? And
>> what does commercial products like WebLogic can normally do?
>>
>> Well, lots of question at my end. Thanks for sharing of your idea. Any
>> thing
>> will help.
>>
>> Best!
>>
>> Li
>>
>> On 12/24/06, Leon Rosenberg <rosenberg.leon@(protected):
>> >
>> > The question is impossible to answer, since you don't tell us what a
>> > user will do :-)
>> > However, to give you an example, if your requests are somewhat
>> > "normal-web-requests" (producing html) than going for 100-150 per
>> > second and server should be a reasonable value.
>> >
>> > regards
>> > Leon
>> >
>> > P.S. Of course it depends hardly on your use-cases... for example your
>> > apache in front of tomcat could reduce the performance by 10% without
>> > giving you anything in exchange.
>> >
>> > On 12/24/06, Li Ma <lima01@(protected):
>> > > I need to setup for a client to run a myspace-like site. My client
>> kept
>> > > asking me how many concurrent user's I can support. I really don't
>> know
>> > the
>> > > answer.
>> > >
>> > > We will use Apache, jk_mod, Tomcat and Oracle(clustered). We will
>> use
>> > X86
>> > > servers with Linux.
>> > >
>> > > Can anyone share your experience and let me know the best load you
>> have
>> > > achieved?
>> > >
>> > > Thanks a lot and Merry Christmas!
>



---------------------------------------------------------------------
To start a new topic, e-mail: users@(protected)
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)