> At the moment, limit simultaneous requests is not ticked - > perhaps I should and set it to 40. I'll try it and let > you know.
Setting it to forty would probably not be an especially good idea - that's an extremely high value. CF is designed to take advantage of queuing requests - some number get simultaneously processed and the rest go into a queue, and are serviced when free threads are available for them. This is supposed to be faster than simply processing all the requests at once (at least in Windows) and it's been my experience that it is, in fact, faster. As Christine Lawson noted, the recommended number is somewhere around 3-7 threads per processor. I'd add the caveat that to find the optimal number, load testing is required, and that you can see significant performance differences between the optimal number and the others. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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 Get the mailserver that powers this list at http://www.coolfusion.com
