Russ Michaels wrote: > doing debugging and load testing on a live production server is generally a > bad idea.
On general principles, sure... although I'd say that a diagnostic reporter like F-R belongs first and foremost on a production box. To the OP... it sounds like you are stuck, so how good is your error reporting? Assuming errors are being thrown at all (you said the server slowed which doesn't necessarily mean its erroring) are you capturing them for review? If not you should put something in to troll and see what comes up. Maybe something unexpected is hanging up threads? If error trapping is out, what about timing the execution of pages and seeing who the hogs are? variables.CFMstart=gettickcount(); ... stuff ... variables.CFMTook=int(gettickcount()-variables.CFMstart); Put start in Application, stop in OnRequestEnd and output to a very small db record that also includes, say, cgi.script_name and cgi.query_string. Leave it up for an hour or three and see what it finds. -- --m@Robertson-- Janitor, The Robertson Team mysecretbase.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:359742 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
