Apple

There is no easy answer.

Ignoring Keep-Alive, you need to manage this setting, the Listen Queue Size, and number of instances to ensure that your app instances don’t build up a backlog of requests that will take longer to process than your users are willing to wait. Otherwise, your instances are going to be calculating responses that are just going to encounter a broken pipe when attempting to respond to the client. That is useless processing. 256 is way, way too high unless you are processing a lot of very short, quick responses. Relating this to the number of Apache processes is pretty meaningless. Apache is not doing much relative to your app.

Request with Keep-Alive complicate this significantly as they tie up a worker thread until the connection is closed.

Chuck

From: <webobjects-dev-bounces+chill=email@hidden> on behalf of Michael Kondratov <email@hidden>
Date: Tuesday, September 13, 2016 at 3:33 PM
To: WebObjects-Dev Mailing List List <email@hidden>
Subject: WOWorkerThreadCountMax

Hello,

Does it make sense to set the value equal to or greater than the number of active apache processes? Our server is receiving more traffic than usual and each application is hitting the default limit of 256. I assume it is due to each apache process trying to maintain a connection to each instance. We typically see apache grow to 1000 processes.

Michael Kondratov

Aspire Auctions, Inc.

216-231-5515

_______________________________________________

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

References:
	>WOWorkerThreadCountMax (From: Michael Kondratov <email@hidden>)