Using debugging information from browser pages
395
The next to last line of the output displays the time that ColdFusion took to parse, compile, and
load pages, and to start and end page processing. This figure is not included in the individual
page execution times. The last line shows the sum of all the time it took to process the request.
Tree execution time format
The tree execution time format is a hierarchical, detailed view of how ColdFusion processes each
page. If a page includes or calls second page, the second page appears below and indented relative
to the page that uses it. Each page appears once for each time it is used. Therefore, if a page gets
called three times in processing a request, it appears three times in the tree. Therefore the tree
view displays both processing times and an indication of the order of page processing.
The tree format looks as follows in the dockable.cfm output format:
As in the summary view, the execution times (in parentheses) show the times to process the listed
page and all pages required to process the page, that is, all pages indented below the page in the
tree.
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.
Summary of Contents for ColdFusion MX
Page 1: ...Developing ColdFusion MX Applications...
Page 22: ...22 Contents...
Page 38: ......
Page 52: ...52 Chapter 2 Elements of CFML...
Page 162: ......
Page 218: ...218 Chapter 10 Writing and Calling User Defined Functions...
Page 250: ...250 Chapter 11 Building and Using ColdFusion Components...
Page 264: ...264 Chapter 12 Building Custom CFXAPI Tags...
Page 266: ......
Page 314: ...314 Chapter 14 Handling Errors...
Page 344: ...344 Chapter 15 Using Persistent Data and Locking...
Page 349: ...About user security 349...
Page 357: ...Security scenarios 357...
Page 370: ...370 Chapter 16 Securing Applications...
Page 388: ...388 Chapter 17 Developing Globalized Applications...
Page 408: ...408 Chapter 18 Debugging and Troubleshooting Applications...
Page 410: ......
Page 426: ...426 Chapter 19 Introduction to Databases and SQL...
Page 476: ...476 Chapter 22 Using Query of Queries...
Page 534: ...534 Chapter 24 Building a Search Interface...
Page 556: ...556 Chapter 25 Using Verity Search Expressions...
Page 558: ......
Page 582: ...582 Chapter 26 Retrieving and Formatting Data...
Page 668: ......
Page 734: ...734 Chapter 32 Using Web Services...
Page 760: ...760 Chapter 33 Integrating J2EE and Java Elements in CFML Applications...
Page 786: ...786 Chapter 34 Integrating COM and CORBA Objects in CFML Applications...
Page 788: ......