User logging on to TPAM experience significant delay requesting passwords.
TPAM admin view TPAM system status and notice all cores running at close to 100%
Appliance feels slow and unresponsive.
Global Setting "Always use cache permissions" introduced in 2.5.910.
Default value = No
Enhancement BFER 8866 created to set default value to = Yes
The reason Always use cached permissions global setting has such a drastic effect on CPU usage has to do with the database views that are the basis for all the permissions granted.
There are two primary views used for the queries. One is a view to an optimized table with indexes tuned for maximum query speed. The second view is the one that is used to build that indexed table and joins Managed Systems, Managed Accounts, Managed Files, Collections, Collection Membership, Assigned Policies, and Global Settings to gather all the information for the optimized table.
The former is the "cached" view, the latter is the "live" view. When users are forced to use the live view, while still indexed for optimal retrieve speed, the server needs to materialize the view for each and every user that needs it. This includes evaluating query plans, setting aside temporary space for sorts, collating results, and so forth. In short - it's a very expensive operation. As opposed to the cached view which simply queries a single table - no joins, expansions, unions - just "select columns from tablename".
Large environments need to ensure this value is enabled and set to "Always use cache permissions" = Yes
Enhancement BFER 8866 created to set default value to = Yes
© 2024 One Identity LLC. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center