"It works by first enabling it (something you would do in your admin and in development only of course) and tweaking the settings. Once enabled, it will print a large set of debug information at the end of very web page. How and what's printed depends on your settings, but it will show things like: Database queries, including the SQL, number of results, and how long the query ran Method executions of components (think classes) and how long they took"
"This information can be incredibly useful in terms of not only finding performance issues but also just realizing what in the heck's actually going on in any one particular request. While useful, this feature of ColdFusion is a bit of a black box. In the past, you could actually build your own debugging templates with modifications to suit your needs, but when I checked recently, that was no longer possible unfortunately."
ColdFusion's debugging output can be enabled in the admin for development and prints extensive per-request diagnostics at the end of each web page. The output can include database queries with SQL, result counts and durations; component method executions and timings; template timings; variables used; and any exceptions thrown during the request. These diagnostics help identify performance bottlenecks and clarify request behavior. Historically debugging templates could be customized, but that capability appears removed. An example shows an included template consuming 6028 ms of a 6055 ms total, clearly pinpointing the source of slowness.
Read at Raymondcamden
Unable to calculate read time
Collection
[
|
...
]