...
| Table | Description |
|---|---|
| Used for database detail pages. Timestamps are identified by the "dbid" parameter. |
| Used for all databases. Timestamps are identified by the database ID. |
| Used for discussion timestamps. Timetamps are identified by the thread ID. |
| Used for Content Repository items. Timestamps are identified by media repository content ID. |
| Used for the Content Repository items of a web initiative. Timestamps are identified by web initiative ID. |
| Used for various XperienCentral objects such as pages and page sections. Timestamps are identified by object ID. For pages this is also the ID in the URL of a page, for example |
| Used for Content Repository terms. When terms are changed they could influence content overviews so they have their own table. Timestamps are identified by term ID. |
...
Debugging the XperienCentral Cache
The cache debugging functionality was introduced in XperienCentral version R24.
You can visually inspect the parts of a content item that have been cached. To do so, you must be logged in to the website backend and the permission "Access debugging tools" in the Permission category "System utilities" must be enabled for your user role. To inspect/debug the cache, navigate to the content item you want to inspect on the website frontend and append the parameter ?cachedebug=true to the end of the URL For example:
https://www.gxsoftware.com/en/products.htm?cachedebug-true
The content item will reload and you will see cached content outlined in red. If you hover the mouse over the area, the cache ID for the content will appear in a tooltip. For example:
...
Performance Checklist
The following checklist can be used to check the performance variables of a XperienCentral website. Performance involves more than XperienCentral and the caching module so other relevant settings are also taken into account.
...