Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Info

The Performance Dashboard was removed from XperienCentral in version R28. Use the Administrative Pages instead.

Anchor
top
top
The XperienCentral Performance Dashboard provides detailed information about how the parts of XperienCentral's infrastructure are functioning. Because XperienCentral is a complex system, the interaction between many different sub-systems and configuration options has a direct impact on how it performs. Using the Performance Dashboard, system administrators, developers, and application managers can quickly identify problems and then make the necessary configuration changes to ensure that XperienCentral performs optimally. The Performance Dashboard measures the speed and response time of page requests and internal queries as well as other settings that affect how XperienCentral runs and rates the results according to the optimal expected results.

...

Performance IndicatorDescription

The functionality/configuration setting is functioning within optimally expected parameters.

The functionality/configuration setting is functioning below its optimal level.

The functionality/configuration setting is having a pronounced, negative impact on XperienCentral's performance and should be immediately examined and addressed.


Note

Notes:

  • In a clustered environment, the statistics shown in the Performance Dashboard are only for the node/instance/server on which the Performance Dashboard is running, not the whole environment.The Monitoring Dashboard allows you to inspect most of the metrics shown in the Performance Dashboard and is also configurable.
  • The Administrative Pages are also useful for closely examining the performance of processes and events within XperienCentral.


To open the Performance Dashboard, navigate to Configuration > Performance Dashboard.

...

If caching is enabled in XperienCentral, a green indicator is shown and if it is disabled, a red indicator is shown. Caching allows XperienCentral to handle the load created by many page requests by using an intelligent mechanism that returns pages without having to regenerate them completely every time they are requested. In all cases, caching improves website performance and it is highly recommended that you enable it for your website.

To enable/disable caching, navigate to the Setup Tool. On the General tab, navigate to the "frontend_system_settings" section and select allow_cache:

...

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 (R30 and older) tab:


Anchor
lowering_page_response_times
lowering_page_response_times
Lowering Page Response Times

...

To enable/disable the XperienCentral debug options that affect performance, navigate to the Setup Tool. On the General (R30 and older) 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.

...