James, everything in this sort of thing is relative, relative to both what you are trying to achieve and why. What I mean by this is for instance do you already have performance issues in an app and if so in comparison to what? I don't think the number of fuses you are using makes things harder, if you have a fuse with a serious problem it could be in no more that 8-10 lines of code and very often is in my experience. Expanded debug is really sort of finer grain in a way, because if you have problems they will show up in the CF errors logs, usually Application and Server. You should start there if you suspect issues and play around with the "Log slow pages" setting in CFAdminstrator and watch the logs. Try starting at 20 seconds and go down till you get some pages showing up, hopefully you won't. Another fine tune facility is "gettickcount" which can be used to get the finer grained times of elements you may suspect are problems.
This is just the tip of the iceberg, web load test tools can also be used to generate load on your application as someone else pointed out but as I said you need to determine what your requirements/benchmarks are in my opinion, hope this is helpful. Mike Brunt, CTO Webapper http://www.webapper.com Tel: 562.243.6255 Instant Messaging AIM: webappermb Webapper, Downey CA Office "Webapper - Making the NET Work" -----Original Message----- From: James Sleeman [mailto:[EMAIL PROTECTED]] Sent: Sunday, May 05, 2002 8:36 PM To: CF-Talk Subject: Finer grain performance indicators Hi all, we all know about the Enable Performance Monitoring flag in the CF debug settings, it throws out some rough information about the processing time of each template used the the request. But it's a pretty rough estimate, below a certain threshold and values are set to 0 for example. Now my coding style (I call it PlugBox, it's a highly bastardized fusebox 2) means that I write applications using many small files - most of them doing very small jobs that take less than that threshold. This obviously makes it a little tricky to performance tune applications. Does any body know a way that a finer grain of performance indication can be achieved ? Take for example the following request... Execution Time 1893 milliseconds 30 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\APPLICATION.CFM 50 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\APP_RUNCORE.CFM 30 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\INDEX.CFM 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PBCORE\APP_BACKSTACK.CFM 441 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PBCORE\APP_CORE.CFM 20 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PBCORE\APP_EXPOSESERVICES.CFM 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PBCORE\APP_FORMURLTOATTRIBUTES.CFM 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PBCORE\APP_HACKERCHECK.CFM 140 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PBCORE\APP_HANDLER.CFM 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PBCORE\APP_HIJACKERCHECK.CFM 100 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PBCORE\APP_LOADCONFIG.CFM 20 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PBCORE\APP_LOADGLOBALSETTINGS.CFM 40 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PBCORE\APP_RUNONCE.CFM 21 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PBCORE\APP_SEARCHCACHE.CFM 10 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PBCORE\APP_STORECACHE.CFM 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PBCORE\LIB_PB_FUNCTIONS.CFM 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PB_BRANCHSETTINGS.CFM 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PB_INPUTFILTER.CFM 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PB_LAYOUTHANDLER.CFM 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PB_LOCALSETTINGS.CFM 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PB_OUTPUTFILTER.CFM 10 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_ADMINISTRATIONLAYOUT\APP_RUNCORE.C FM 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_ADMINISTRATIONLAYOUT\DSP_ADMINISTR ATIONLAYOUT.CFM 20 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_ADMINISTRATIONLAYOUT\PB_HANDLER.CF M 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_ADMINISTRATIONLAYOUT\PB_LOCALSETTI NGS.CFM 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_ADMINISTRATIONLAYOUT\PB_OUTPUTFILT ER.CFM 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_ADMINISTRATIONLAYOUT\PB_PROVIDES.C FM 10 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_ADMINISTRATIONLAYOUT\QRY_ADMINISTR ATIONLAYOUT.CFM 50 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_WEBPAYACCOUNTS\APP_RUNCORE.CFM 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_WEBPAYACCOUNTS\CHILD.CFM 10 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_WEBPAYACCOUNTS\CHILDREN.CFM 160 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_WEBPAYACCOUNTS\FIELD.CFM 140 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_WEBPAYACCOUNTS\FIELDSET.CFM 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_WEBPAYACCOUNTS\PB_BRANCHSETTINGS.C FM 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_WEBPAYACCOUNTS\PB_INPUTFILTER.CFM 121 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_WEBPAYACCOUNTS\PB_LOCALSETTINGS.CF M 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_WEBPAYACCOUNTS\PB_OUTPUTFILTER.CFM 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_WEBPAYACCOUNTS\PB_PROVIDES.CFM 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_WEBPAYACCOUNTS\PLUGIN_WEBPAYSITES\ ACT_EDIT.CFM 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_WEBPAYACCOUNTS\PLUGIN_WEBPAYSITES\ APP_RUNCORE.CFM 10 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_WEBPAYACCOUNTS\PLUGIN_WEBPAYSITES\ CHILDREN.CFM 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_WEBPAYACCOUNTS\PLUGIN_WEBPAYSITES\ DSP_EDIT.CFM 10 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_WEBPAYACCOUNTS\PLUGIN_WEBPAYSITES\ DSP_FORM.CFM 70 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_WEBPAYACCOUNTS\PLUGIN_WEBPAYSITES\ FIELD.CFM 70 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_WEBPAYACCOUNTS\PLUGIN_WEBPAYSITES\ FIELDSET.CFM 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_WEBPAYACCOUNTS\PLUGIN_WEBPAYSITES\ PB_BRANCHSETTINGS.CFM 130 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_WEBPAYACCOUNTS\PLUGIN_WEBPAYSITES\ PB_HANDLER.CFM 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_WEBPAYACCOUNTS\PLUGIN_WEBPAYSITES\ PB_INPUTFILTER.CFM 60 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_WEBPAYACCOUNTS\PLUGIN_WEBPAYSITES\ PB_LOCALSETTINGS.CFM 0 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_WEBPAYACCOUNTS\PLUGIN_WEBPAYSITES\ PB_OUTPUTFILTER.CFM 10 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_WEBPAYACCOUNTS\PLUGIN_WEBPAYSITES\ PB_PROVIDES.CFM 110 msD:\JOBS\MEGAMALL\MEGAMALL\WEBPAY\PLUGIN_WEBPAYACCOUNTS\PLUGIN_WEBPAYSITES\ QRY_FORM.CFM 0 msSTARTUP, PARSING, & SHUTDOWN I can see roughly what is taking the time in this request, but it is very rough, it would be nice to see that for template bar.cfm 10ms was spent processing tag <CFFOO/> or even just return something useful instead of 0 for those very quick templates. It would also be better if multiple calls to the same template were not lumped togethor, for example in the above all the templates in \PBCORE\ get run multiple times (4 times if I count correctly) but they each only get one time. Ideas ?? --- James Sleeman Innovative Media Ltd Ph: (03) 377 6262 http://www.websolutions.co.nz CAUTION: The information contained in this email message is confidential and may be legally privileged. If the reader of this message is not the intended recipient you are notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immediately and destroy the original message and any attachments. Views expressed in this communication may not be those of Innovative Media Ltd. ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
