Re: URGENT issues with CLOSE_WAIT states
Re: URGENT issues with CLOSE_WAIT states
- Subject: Re: URGENT issues with CLOSE_WAIT states
- From: Paul Lynch <email@hidden>
- Date: Mon, 3 Apr 2006 17:42:32 +0100
On 3 Apr 2006, at 17:05, Sacha Michel Mallais wrote:
On Apr 2, 2006, at 5:03 PM, Corin Lawson wrote:
I would like to know what kinds of limits there are for load on
WO. How many instances of an application could I run, has anyone
much experience with high loads, say 1000's of requests in the
space of a few minutes? Java Monitor seems cumbersome with 100
instances.
The most important thing is to have enough memory to hold the
number of instances you want. With 2GB of RAM, that likely means
less than 20 or 30. 100 is probably right out unless they are very
small apps. How does your machine respond under 100 instances?
How often is it swapping?
Indeed.
I can remember an app handling around 100 transactions per second
with a single server (http, database and application), with 1.0 - 1.5
Gb RAM and roughly 10 instances (less than 20, certainly). This
would have been an ObjC version of WebObjects, probably around 3.5.
Paul
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden