...
| Indicator | Description |
|---|---|
| Largest response time | The largest response time in milliseconds for all page requests across the entire web site. To view the response time for individual pages, see Page Response Time. |
| Largest query execution time | The largest query execution time is the execution time of the longest of all SQL queries performed on all databases. To view the query execution time for individual queries, see Queries. |
| Largest response time Page Generator | The largest response time in milliseconds the Page Generator took to fulfill a request. To view the Page Generator response time for individual pages, see Page Response Time. |
| Average response time Page Generator | The average response time in milliseconds that the Page Generator took to fulfill requests. To view the Page Generator response time for individual pages, see Page Response Time. |
| Average response time | The average response time in milliseconds for all page requests.To view the response time for individual pages, see Page Response Time. |
| Average query execution time | The average query response time is the average for all SQL queries performed on all databases. To view the query execution time for individual queries, see Queries Indicators. |
Settings
The settings tab shows the status of XperienCentral settings that can affect performance. In the "Status" column, you can click the orange and red indicators for more information on the meaning of the indicator itself and what you can do in order to improve the performance for the related item.
...
The caching module of XperienCentral stores a timestamp in the timestamp database for each cached web page. This timestamp is needed in order to determine whether the web page needs to be regenerated or whether it can be retrieved from the cache. For high volume websites, the number of web page requests per second can be so high that even the relatively simple task of performing one SQL query to retrieve this timestamp from the database can cause a bottleneck. If this exceeds 500 milliseconds, it may indicate a performance issue.
To prevent timestamp retrieval from becoming a bottleneck, timestamps can be cached in memory for <n> milliseconds. Note that this also causes a delay of <n> milliseconds; during the <n> milliseconds, modified web pages will not be regenerated. It is recommended that you set timestamp caching to at least 5000 milliseconds (5 seconds). If you set timestamp caching to fewer than 5000 milliseconds, this can cause database bottlenecks especially for websites that experience a large number of page requests.
Timestamp caching is configured in the XperienCentral Setup Tool. Navigate to the "frontend_system_settings" section of the [General] tab:
| Anchor | ||||
|---|---|---|---|---|
|
...
To enable/disable the XperienCentral debug options that affect performance, navigate to the Setup Tool. On the [General configuration] tab, navigate to "development_settings". Clear the checkbox for enable_debug_messages. In a production environment, the setting enable_view_resolve_cache should be selected.
...