I have noticed that the number of worker threads immediately goes us when we set connection pool to 1. If it is set to zero, worker threads stop at about 70, but we see 50% system time CPU utilization. Once pooling is enables, CPU utilization drops, but workers grow to the max setting.
Michael Sent from my iPad > On Sep 13, 2016, at 6:44 PM, Michael Kondratov <[email protected]> > wrote: > > Chuck, > We are handling around 100 requests per second spread over 5-10 > application instances. We do have KeepAlive enabled in Apache. How would I > manage that in WO? If the application thread count grows to 300 threads or > so, does it mean that at one time we had a back log of ~250 requests or so? > > Michael Kondratov > Aspire Auctions, Inc. > 216-231-5515 > >> On Sep 13, 2016, at 6:40 PM, Chuck Hill <[email protected]> wrote: >> >> 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: <[email protected]> on behalf >> of Michael Kondratov <[email protected]> >> Date: Tuesday, September 13, 2016 at 3:33 PM >> To: WebObjects-Dev Mailing List List <[email protected]> >> 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 protected]) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/chill%40gevityinc.com >> >> This email sent to [email protected] > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/michael%40aspireauctions.com > > This email sent to [email protected]
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
