> Well, for one, I want to see what cf pages are being hit in > real time, but mostly because if I have an errant template or > something spiralling out of control, I want to find out which > one it is. > > I was writing one page not too long ago, can't remember what > I was doing, but as soon as it would run, cfas memory usage would > skyrocket until the server hung... It was immediately apparent > which script was causing the commotion...
If the problem is contained within a single script, wouldn't this show up during QA/debugging? In general, I've found the "log slow pages" option useful for finding problem scripts, on sites that can't be performance tested. On sites that can, the load-testing tool will tell you what pages are slow, or have other problems - which is why load testing is vital. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
