Views: 1850 (Data available since 06.02.2017)
Last Modified: 22.06.2015

The following pages comprise the user interface of the Performance Monitor module in Control Panel:

You will find below the Performance folder (select Settings > Performance).


Pages

To view the page traffic data, use the “Performance monitor: Pages” form (Settings > Performance > Pages):

Performance monitor: pages

You can view all the hits done to a page by clicking the page name link. Effectively, this opens the hits statistics form.


Hits

The “Performance monitor: Hits” form (Settings > Performance > Hits) shows the hits report:

Performance monitor: hits

Beside each page, you will find a link shown as two angle brackets (>>). Use it to open a corresponding page in the public section and view the page statistics:

A more detailed report is also available. Click Performance on the public section toolbar (or select Statistics summary in the button drop-down menu):

Wait until the hits summary is loaded, then find a required page and click a link (>>) to view the detailed statistics information:

To view all the SQL queries performed by a hit page, click the page name link or a respective number in the Queries column.

To view the components used by a hit page, click a number in the Components column.


Components

The “Performance monitor: Components” form (Settings > Performance > Components) shows information about components and include areas used by the website pages:

Performance monitor: Components

To view all the SQL queries made by a component, click a number in the Queries column.


SQL Queries

The “Performance monitor: Queries” form (<Settings > Performance > SQL Queries) shows summary of all performed SQL queries:

Performance monitor: Queries

Note that this report is available only if the Log queries option is enabled in the Performance Monitor module settings.

To view the query runtime details, double-click the row showing a required query. This will open the query information in a new window:

Query execution plan


Tables

When debugging a dynamic website, one of the most essential information a web developer needs is the database structure and the database table dynamics. To view the database tables summary, open Settings > Performance > Tables:

Tables

You can view the contents of a database table, click the table name link.

The system keeps track of the most recently viewed tables and makes them available for faster access in the context toolbar. To view one of the recently accessed table, select it in the Recently browsed tables.

The following group actions can be applied to the selected tables:

Group actions


Since version 11, it is possible to select rows from bound tables by filter. This feature is now supported for the Search module, those displaying contents of information blocks, and tables with ratings.

Consider the following example. Assume you have picked all the records with ID of 871 (in fact, the only records because the ID’s are unique).

Navigation;

Now, if you select a table in the action menu, say b_search_content_stem, the system will select rows in b_search_content_stem whose SEARCH_CONTENT_ID is 871:

Navigation

You can hover the mouse pointer over the field values to view information stored in a table:


PHP Settings

The “Performance monitor: PHP Settings” form (Settings > Performance > PHP) shows the summary of the operating environment.

Performance monitor: PHP Settings

Click the PHP Settings link to view the standard (phpinfo) page.


Database server

The “Performance Monitor: DB Server” form (Settings > Performance > DB Server) shows the database server performance statistics, comments and/or recommendations:

Performance Monitor: DB Server


PHP Errors

The “Performance Monitor: PHP Errors” form (Settings > Performance > PHP Errors (N)) registers and shows all the PHP errors a system encountered while running the website.

Note that this report is available only if the Log PHP warnings option is enabled in the Performance Monitor module settings.



Courses developed by «Bitrix», Inc.