You can adjust the trade-off between performance and memory usage by managing the caching of system objects. Performance improvements are not significant, but you can decrease the cache size to allow RSA Authentication Manager to reallocate memory for other purposes, or you can increase the cache size to avoid reloading information from the database.
The value in the Cached Objects field is the maximum number of objects allowed in the cache. This value must be between 3 and 10 million. When the number of cached objects exceeds this limit, the cached object that has been unused for the longest length of time is deleted to make space for new objects.
Use the Current Utilization field as a guide when setting the number of objects to cache. For example, if AdminRoleCache is set to 5000, but your current utilization is only 3, you might choose to lower the AdminRoleCache setting. Make sure to check the current utilization values during a peak utilization period.
Use the Refresh Interval field to specify how often to refresh each type of cached object.
You can flush the cache to remove old information from memory. For instructions, see Flush the Cache.
Cache settings are instance-based, but the primary instance settings can be applied to all replica instances. Cache configuration settings might not be immediately visible through the replica instance. Data should replicate within 10 and 20 minutes.
Before you begin
You must be a Super Admin.
In the Security Console, click Setup > System Settings.
Under Advanced Settings, click Caching.
Select an instance.
Enter the cache size that you want in each of the Cached Objects fields.
Enter the refresh interval setting for each type of cache object in the Refresh Interval field.
If you configured the primary instance, you can choose to apply the same settings to all replica instances.
We want your feedback! Tell us what you think of this page.