On Mar 4, 2008, at 1:56 PM, Art Isbell wrote:
On Mar 4, 2008, at 11:29 AM, Chuck Hill wrote:
On Mar 4, 2008, at 1:20 PM, Mike Schrag wrote:
Max had some really good info on all these values in the WO
scalability session from a few WWDC's ago ... He talked about how
the defaults are actually really terrible and will make your app
fall over under load. Does anyone have their notes from that? It
was really useful info that's hard to find anywhere else.
IIRC he said about 7-8 worker threads and 2-3 listen queue ones.
Of course that depends on your app and what average requests are
doing etc etc. But above that limit, if the app slows, the
requests pile up to where it has no hope of meaningful recovery
(the app may recover, but the users have gotten an error message
long before).
Based on Max's comments, I have set the listen queue size to 2,
minimum adaptor threads to 2, and maximum adaptor threads to 4 on my
deployed WO apps. Yes, these seem extremely low compared with the
defaults, but as Chuck (and Max) stated, higher values can cause
poor performance at high loads. With these low settings, you'll get
a warning at app startup, but ignoring this warning hasn't caused
any obvious problem.
Performance tuning is a bit of a black art
That it is. The results are very often not what you predict. There
are several things that interplay and changing one can greatly affect
the others.
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
