>but I think at >the very least it shows that 200 simultaneous threads is massive overkill.
Ok, already :-) Forget 200 - I've reset it to 96. Now, to everyone who is saying that 96 is too high my own experience of trying to keep the site running smoothly at all costs is that an SRR of 96 is *way* better than 20. This is experience of coping with overloads on a daily basis for 3 weeks or so. It does not reduce the number of times the number of running threads grows (nor does it increase it), but it does reduce dramatically the number of times that cfmx has to queue threads and the recovery when it is not queuing is much faster than when it is. With SRR set to 20 it was not unusual to have cfmx queuing 20 times a day or more. Almost every timed it queued I had to intervene. Now 2 or 3 is the norm, and the 17 other times when the thread count grows it recovers quickly without queuing. I now have to intervene once or twice a day (though unfortunately I still have to watch it like a hawk!). (By intervene I mean restrict the max number of connections in IIS down to about 300. cfmx recovers, I reset the connections to unlimited). This business about 4 threads per processor is from CF 4 days. Surely the calculation is different with cfmx, simply because it's a completely different engine? Alan ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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 Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
