> I'm a bit confused now. > On one hand Adobe recommends number of simultaneous requests = > num_of_CPU_cores * 4 or 5 which is 16 - 20 requests on Quad Xeon CPU. At > least it was so for CF 7/8/9.
This isn't really correct. To the best of my knowledge, there are no formal recommendations from Adobe on proper settings for number of simultaneous requests, and there have never been any. Everybody wants some, but unfortunately there's no "one size fits all" number for this. If you want to optimize this for your application, you need to load test it with your application. > On other hand latest recommendations from Adobe are connection_pool_size = > 500 for two_sites_conf and it sets simultaneous Template requests = 500 in > CF admin. I'm curious, can you provide a citation for this recommendation anywhere? > Could anybody clarify what is a best values for connection_pool_size and > how it is connected to simultaneous Template requests in CF admin? Well, my understanding of it is: the web server looks at each incoming request, then sends it to the connector if the URL of the request matches the pattern specified in the context root. By default, the context root is "/", which means that every request matches, and all are sent to the connector. The connector evaluates the request to see if it matches a servlet pattern specified in web.xml. If it doesn't, it's returned to the web server for processing. So, it would make sense that the connector would require a much larger pool of simultaneous requests than CF itself would. > So question is: what connection pool settings do you use in your production > sites? > If you use 500 connection_pool_size/simultaneous_template_requests, how > stable is your production site in case of peak load with a lot of requests > coming simultaneously? I'd honestly have to go look that up, but I doubt very much that the use cases for the largest production sites I've worked on match the use cases for your sites. In other words, like every other CF setting, you either (a) leave it at the default values, or (b) use load testing to determine the best fit for your application. In my case, the large production sites in question are primarily CMSs, and dynamic content is reached through reverse proxies (making the connection pool settings for the connector much less important - they can be fairly low since static requests have already been removed from the equation). Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ http://training.figleaf.com/ Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on GSA Schedule, and provides the highest caliber vendor-authorized instruction at our training centers, online, or onsite. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:356980 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
