informal load testing and decided that the default of 10 was reasonable.
Performance started getting worse about 15 or so, though the processors were
still spinning full bore. We opted to leave it high, as the app running on
there does a fair amount of non-local "stuff" (DB access, web service calls,
etc), where there is significant potential for requests to be waiting on
external resources, not processor time.
Not sure if that's of any value other than to say "higher isn't necessarily
bad", but who knows.
Cheers,
barneyb
> -----Original Message-----
> From: Matt Robertson [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 05, 2004 3:15 PM
> To: CF-Talk
> Subject: CF 6.1 simultaneous requests - optimum guesstimate?
>
> In olden times the general/generic recommendation for the
> "Maximum number of simultaneous requests" setting in CF Admin
> was the number of processors times 2 minus 1. So a dual
> processor would be set for 3, and a single processor would
> run 1 or, if you were the rakish/daring sort, 2.
>
> Default settings were WAY over this and recommendations to
> crank those settings down seemed to stabilize a lot of stuff,
> based on forum/list posts at the time.
>
> Well now I'm running CF 6.1 everywhere and I thought it'd be
> smart to ask again what y'all think is best workable with
> current CF versions.
>
> General ideas for CF 6.1 Standard? Any different for CF 6.1
> Enterprise? Is there a firm guideline or is it still YMMV
> (Your Mileage May Vary)?
>
>
>
> --
> -------------------------------------------
> Matt Robertson, [EMAIL PROTECTED]
> MSB Designs, Inc. http://mysecretbase.com
> -------------------------------------------
>
> --
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
