User Guide

Table Of Contents
430 Chapter 18: Debugging and Troubleshooting Applications
By looking at this output in this figure you can determine the following information:
ColdFusion took 0 ms to process an Application.cfm page as part of the request.
The requested page was tryinclude.cfm. It took 203 ms to process this page and all pages
required to execute it. The code directly on this page took 71 milliseconds (203 - 93 - 16 - 23)
to process.
The mytag2.cfm page was processed three times. All processing took 93 milliseconds, and the
average processing time was 31 milliseconds. (This page does not call any other pages.)
The mytag1.cfm page was processed two times. All processing took 78 milliseconds, and the
average processing time was 39 milliseconds. This time included the time to process
mytag2.cfm (this tag calls the mytag2 custom tag); therefore, the code directly on the page
took an average of 8 milliseconds and a total of 16 milliseconds to process.
The includeme.cfm page took about 62 ms to process. This processing time includes the time
to process the mytag1.cfm, and therefore also the time to process mytag2.cfm once. Therefore
the code directly on the page took 23 milliseconds (62-39) to process.
ColdFusion took 125 ms for processing that was not associated with a specific page.
The total processing time was 328 milliseconds, the sum of 125 + 203.
Database Activity
In the Administrator, when Database Activity is selected on the Debugging Settings page, the
debugging output includes information about database access.
SQL Queries
The SQL Queries section provides information about tags that generate SQL queries or result in
retrieving a cached database query:
cfquery, cfinsert, cfgridupdate, and cfupdate. The
section looks like the following figure in the dockable.cfm output format: