JMX Measures for Caching in Tests

JMX information for the Tests tree cache and the filter cache can be found on your front-end server in the JMX measures tree at borland.com/Frontend/TM.

Tests Tree Cache Measures

Two primary measures are available for the Tests tree cache. TestPlanTreeCache only delivers a measure, NumberOfCachedProjects, on how many projects are currently cached. All details of the cache of the project are available from the second measure, TestPlanTreeCache_<number>. This measure is actually made out of the following measures:

Measure Description
Hits The number of times the cache was used, and database requests were not required.
LastUpdateCheckDurationInMillis The duration in milliseconds the last update took, see LastUpdateCheckTime, to check for updates in the database.
LastUpdateCheckTime The time when the last update check occurred.
LastUpdateDurationInMillis The duration in milliseconds the last update took, see LastUpdateTime, to update the cache after a change occurred.
LastUpdateTime The time when the last update to the cache occurred due to a change in the Tests tree.
TreeInitializationTimeInMillis The duration in milliseconds it took to load the whole project tree into the cache. This value will not change as long as the project cache is loaded.
TreeSize The number of test nodes, which are test containers, test folders, and tests, in the project.
UpdateChecks The number of checks for changes of the Tests tree for this project since the project tree cache was initialized.
Updates The number of updates of the cached tree due to changes in the Tests tree.

Test Filter Cache Measures

The TestPlanFilterCache measure is comprised of the following three measures:

Measure Description
Hits The number of times the cache was used and no separate execution of the filter on the database was necessary.
Misses The number of times the filter cache was not used, but the filter was executed against the database.
Size The current number of cached filter results.