You use the Diagnostics module for profiling of various time-intensive operations such as HTTP requests, background tasks, database queries, and page compilations. Each Diagnostics profiler collects data on a specific set of performance indicators and provides you with report that may identify performance issues and bottlenecks.
EXAMPLE: You want to check how a certain action is executed, for example - opening a news item and leaving a comment.
To get a report, you first start related profilers (database, HTTP requests), execute the action, stop profiling, and view the report.
The following table summarizes the Diagnostics module profiling tools and their settings.
IMPORTANT: Database profiling can generate a lot of tracing data in a short period of time. When you are not actively collecting diagnostic data, be sure to stop the database profilers.
NOTE: A profiler tool is not necessarily bound to provide data for one report only. For example, the System Operations tools provides data for both the HTTP requests and Background tasks reports. For more information, see Diagnostics reports.
On the Profilers page, you can:
Back To Top