Maximum number of simultaneous requests

[blorg]

Does anyone have any current thoughts/personal stories on things to try with
this setting; most of the references that I can find date to 2004 and of course
CFMX7 is new since then.

Certainly the suggestion
[url]http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=tn_18540[/url] for "3 per
processor" seems very low indeed. Currently we are at 16 on a dual-processor
Xeon 3Ghz, currently serving over 1.1m (all db-generated) pages per day. This
is one of two boxes hanging off a seperate SQL Server (neither of the other two
are particularly stressed.)

Our main "issue" beyond general load on this box (which is high) is a periodic
job on the database that refreshes a denormalised table (we are using this for
performance reasons.) This locks reads out for the period of the refresh (was a
few seconds but now can be nearer 30-45) and if load is particularly high at
that point it has in the past sent the queued requests up into the hundreds
never to return. I'm also looking at approaches to doing this on the database
side that avoids the whole read locking problem in the first place.

But even beyond this with increased load we are now seeing the queued requests
climbing even outside this refresh period.

[ke4pym]

16 should be okay on your machine. Less is better for this option box. We're
running 14 and serving 3.5m pages/day on similar hardware. Do you limit the
connections in your datasources? Thought about another CF server (or going
Enterprise with another instance)?

There is really only a couple ways to deal with queued requests. The main one
is make the requests go faster. Streamline/scale your code or buy more/bigger
hardware or get rid of the users ;)

[LL@Work]

[url]http://www.talkingtree.com/blog/index.cfm/2005/2/7/CFMX7JRunSimReqs[/url] is a blog entry from one of our engineers that provides some good detail.

[blorg]

Thanks for the replies. Looks like my best bet is to experiment with a few
different settings. I do think that the server is pretty much at its limit and
we are in the process of moving to a more extensive setup where we will load
balance over three or four CF servers but right now I am looking at stopgap
measures to keep this server alive until we can make this move.