Hi.
I run CF5 on Win2k. I have enabled 'Show Total Processing Time', or
exploded benchmarking, or whatever you want to call it.
In customtags that use <cfexit> the execution
time of the calling tag will be attributed to the custom tag itself rather
than the calling tag. This makes the debugging output totally useless.
To reproduce, create two templates, exit.cfm and test_exit.cfm (in the
same directory). The file exit.cfm should contain just a single <cfexit>
statement. The test_exit.cfm should be something that calls the exit.cfm
as a custom tag and then does something that takes a long time.
To be precise:
exit.cfm:
<cfexit>
test_exit.cfm:
<cf_exit>
<cflock name="z" type="readonly" timeout="0">
<cflock name="z" timeout="1" throwontimeout="0">
</cflock>
</cflock>
(the cflock thingy will put coldfusion to sleep for one second)
The debugging output shows: (edited to remove file locations)
Execution Time
1016 milliseconds
0 ms ...\APPLICATION.CFM
1000 ms ...\EXIT.CFM
0 ms ...\TEST_EXIT.CFM
16 ms STARTUP, PARSING, & SHUTDOWN
Note that CF has accredited the 1000 ms to exit.cfm and not test_exit.cfm!
______________________________________________________________________
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/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
