RSA Caches Test

Cache that is right-sized and well-used can significantly enhance performance of the RSA Authentication Manager! The cache is said to be effectively utilized only if it is able to service the maximum number of requests to the RSA Authentication Manager; this greatly reduces direct disk accesses and related overheads, and thus improves performance. On the contrary, ineffective cache usage can be the key contributor to a slowdown or degradation in performance, as it increases disk accesses. To understand how the caches are utilized and to promptly capture abnormalities in cache usage, administrators have to continuously monitor the size of each cache. If the cache is not updated for a prolonged time period, then the requests served by the cache may contain obsolete entities. This may cause old policies and data of user group to be pushed to the end users, which in turn may pose a serious security thread to the enterprise's data.

This test monitors each cache of the RSA Authentication Manager and reports its usage - both in terms of size and its request serving ability. In the process, the test proactively alerts administrators to the under-utilization and improper size of the cache, and helps them quickly initiate corrective measures.

Target of the test : A RSA Authentication Manager

Agent deploying the test : An external agent

Outputs of the test : One set of results for each cache of the RSA Authentication Manager being monitored

The figure below depicts the test configuration page of this test. Click on the parameters in the figure below to know what they are and how to configure them.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Cache size

Indicates the total size of this cache.

MB

 

Cache hit ratio

Indicates the percentage of authentication requests that were successfully retrieved from this cache.

Percentage

A high value is desired for this measure.

Cache flush count

Indicates the number of times this cache was flushed.

Number

Cache is flushed to remove old information from memory. When the cache is flushed, each selected object is refreshed from the database the next time it is accessed.

Cache contents are refreshed every 10 minutes. Depending on cache settings, database replicated changes to cached data may take up to 10 minutes to display on all instances after a change occurs on the primary. If you do not want to wait for the automatic 10-minute refresh, you can flush the cache on each individual instance.