ColdFusion MX 6 1 Setting: Maximum number of simultaneous requests

CFMX 6.1 Setting: Maximum number of simultaneous requests Default is 25, I've head of folks using 1000. How is yours set? Why? We're having an issue with requests getting stacked up and taking forever to run as a result. The user continues to click the same link, adding to the problem, yadda, yadda.... What is a good rule of thumb? We are running on a 3 GIG box,1 GIG of ram, Win2k, CFMX 6.1 Standard.

We set ours to 12.  Picked it after some informal load testing at different levels (from 5 to 40), and that seemed to give us the best mix of not getting stacked up, and getting out of stacked up fast when it did get stacked (because of less thread contention). That's on dual Xeons (hyperthreaded) with a gig of RAM, Linux, Apache, CFMX 6.1 Standard. I suspect that people setting it at 1000 simply though "bigger is better", because a thousand clients at a time is more capacity than 25 at a time, negelecting to consider the finite resources to share between requests. Cheers, barneyb ----- Excess quoted text cut - see Original Post for more -----

A 1000 simultaneous requests would equal one big pile of "current users".  I doubt that any single server could hold up under that load. Please check my math and see if this is correct. If each page is 20K * 1000 simultaneous requests = 20000K = 20MB that is a whopping lot of data to ask any server to dish out Or for that matter any internet connection to handle. Mark W. Breneman -Cold Fusion Developer -Network Administrator   Vivid Media   mark@vividmedia.com   www.vividmedia.com   608.270.9770   _____ Sent: Wednesday, April 28, 2004 1:47 PM To: CF-Talk Subject: CFMX 6.1 Setting: Maximum number of simultaneous requests CFMX 6.1 Setting: Maximum number of simultaneous requests Default is 25, I've head of folks using 1000. How is yours set? Why? We're having an issue with requests getting stacked up and taking forever to run as a result. The user continues to click the same link, adding to the problem, yadda, yadda.... What is a good rule of thumb? We are running on a 3 GIG box,1 GIG of ram, Win2k, CFMX 6.1 Standard.   _____  

To answer that question in a more official manner, there is no answer that works for everyone. If you website only uses CF to display "Today's date is #now()#" then you can have a lot more of simultaneous requests then a website that uses tons of calls to a database and tons of CF code. Check out cfstat , watch your "Req Q'ed" and adjust your simultaneous requests accordingly. http://livedocs.macromedia.com/coldfusion/6.1/htmldocs/basico25.htm Mark W. Breneman -Cold Fusion Developer -Network Administrator   Vivid Media   mark@vividmedia.com   www.vividmedia.com   608.270.9770   _____ Sent: Wednesday, April 28, 2004 2:58 PM To: CF-Talk Subject: RE: CFMX 6.1 Setting: Maximum number of simultaneous requests A 1000 simultaneous requests would equal one big pile of "current users".  I doubt that any single server could hold up under that load. Please check my math and see if this is correct. If each page is 20K * 1000 simultaneous requests = 20000K = 20MB that is a whopping lot of data to ask any server to dish out Or for that matter any internet connection to handle. Mark W. Breneman -Cold Fusion Developer -Network Administrator   Vivid Media   mark@vividmedia.com   www.vividmedia.com   608.270.9770   _____ Sent: Wednesday, April 28, 2004 1:47 PM To: CF-Talk Subject: CFMX 6.1 Setting: Maximum number of simultaneous requests CFMX 6.1 Setting: Maximum number of simultaneous requests Default is 25, I've head of folks using 1000. How is yours set? Why? We're having an issue with requests getting stacked up and taking forever to run as a result. The user continues to click the same link, adding to the problem, yadda, yadda.... What is a good rule of thumb? We are running on a 3 GIG box,1 GIG of ram, Win2k, CFMX 6.1 Standard.   _____   _____  

Don't forget that simultaneous requests (the running request pool) does not itself correspond to the number of active users.  ColdFusion uses a queue, with queue size (maxHandlerThreads) and queue timeout (threadWaitTimeout) defined in jrun.xml, to feed the running request pool.  The queue buffers the incoming requests while feeding the request pool where the rate of clearance through the request pool is the throughput.  If the simultaneous request size is modulated over a range during load testing, a peak should be identified which defines optimal throughput for that hardware configuration and application design.  Setting simultaneous requests too high shifts throughput to the right of the peak and will cause the CPU to thrash as the overhead of managing so many running requests competes with actually executing them.   _____ Sent: Wednesday, April 28, 2004 3:58 PM To: CF-Talk Subject: RE: CFMX 6.1 Setting: Maximum number of simultaneous requests A 1000 simultaneous requests would equal one big pile of "current users".  I doubt that any single server could hold up under that load. Please check my math and see if this is correct. If each page is 20K * 1000 simultaneous requests = 20000K = 20MB that is a whopping lot of data to ask any server to dish out Or for that matter any internet connection to handle.