That's for simultaneous worker threads. I think the number is up a bit with CFMX, and the optimal number actually varies quite a bit from app to app.
However, simultaneous threads is also a lot different than simultaneous connections. Unprocessed threads just go into the queue. If an app typically processes a page in 200ms, then a single thread can handle 5 "simultaneous" connections and respond to all within one second. Drop the typical page time to 50ms (easier said than done), and you've got a lot more "simultaneous" connections. Sam > -----Original Message----- > From: Benjamin S. Rogers [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, November 19, 2002 2:17 PM > To: CF-Talk > Subject: RE: ColdFusion practical limits > > > > 2000 simultaneous transactions > > Maybe I'm missing something, but it used to be that Allaire > recommended (as a general rule) limiting the simultaneous > transactions to 4 x the number of CPUs. Of course, that goes > back to ColdFusion 4 and early Pentium IIs, and there were > lots of other variables to take into consideration. > Nevertheless, even if that number has grown to, say, 20 for > your average Web server, and you have dual processor boxes > (still the best bang for the buck?), that would be 50 servers. > > Benjamin S. Rogers > http://www.c4.net/ > v.508.240.0051 > f.508.240.0057 > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
