Apple

On Thu, Mar 24, 2011 at 8:18 PM, Kieran Kelleher <email@hidden> wrote:

On Mar 24, 2011, at 10:50 AM, Rafal Szczepanski wrote:

Hi All,

I would like to ask you about the optimal number of WorkerThreads (application settings: WOWorkerThreadCountMin & WOWorkerThreadCount).

One of the my applications is serving sometimes more than 2000 pages per hour.

The current setting is 16 WorkerThreads but I noticed that from time to time this number is not enough and the server is creating more WorkerThreads which is freezing for a while the application.

Do you know if the number of WorkerThreads affects application’s performance? If not then perhaps I should start with 256 right from the beginning….

More WorkerThreads = more concurrent requests.

Application performance in general is improved by more memory, faster CPU and fast/optimized database. Check WOStatistics page for average and max response times as a start to seeing where your slow pages are. Examine your slow query logs of your database, etc.

There are few pages that for sure require an optimization but it seems that the source of my problem (need for more than 16 WorkerThreads) was a bit different. There was one page that was querying the database and couldn't receive the result. This was causing other WorkerThreads to wait for this request's WorkerThread and when new requests were coming that could not be processed WebObjects were creating additional WorkerThreads.

I’ve got also another question do you know some real life examples of applications built in WebObjects that are serving huge number of requests/heavy load?

real life example = iTunes Music Store

That's a "huge" example :-) I suppose though that having developers that built WebObjects might have made some things easier...

Cheers,
Rafal

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)

This email sent to email@hidden