Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

What is the maximum number of user update / technical rules you have seen in a Saviynt instance?

Regular Contributor
Regular Contributor

I just want to get an idea how many rules Saviynt can handle without running into performance issues.

How many rules can we create without worrying about issues like performance problems and skipped users where rules fail to evaluate?



The performance of Saviynt, like any other Identity Governance and Administration (IGA) tool, can be influenced by several factors including the complexity of the rules, the underlying infrastructure, the volume of data, and how well the system is optimized. However, Saviynt is designed to handle a large number of rules and extensive data sets efficiently.

  1. Infrastructure and Environment:

    • The performance of Saviynt is significantly dependent on the infrastructure on which it is deployed. A robust infrastructure with adequate CPU, memory, and storage resources can handle more rules without performance degradation.
    • Cloud-based deployments (e.g., on AWS, Azure) can leverage the scalability of the cloud to manage performance effectively.
  2. Rule Complexity:

    • Simple rules that require straightforward evaluations (like basic attribute comparisons) will have less impact on performance compared to complex rules that involve multiple conditions, cross-referencing large datasets, or involve complex logic.
    • Performance may degrade if rules involve intensive operations, such as regular expression matching on large data sets or extensive database queries.
  3. Volume of Data:

    • The number of users, entitlements, and the overall data volume directly impacts performance. A higher volume of data increases the computational load during rule evaluations.
    • Regular data archiving and pruning of inactive records can help maintain performance levels.
  4. Optimization and Best Practices:

    • Efficient rule design, such as combining multiple conditions into single rules where possible, can reduce the overhead.
    • Indexing relevant database fields and optimizing database queries can significantly improve performance.
    • Regular monitoring and tuning of the system based on usage patterns can help maintain performance.

Practical Experience and Recommendations:

  • While there is no fixed number of rules that can be handled without issues, anecdotal evidence from various organizations using Saviynt suggests that well-optimized environments can handle hundreds to thousands of rules.
  • Users have reported managing over 1,000 rules effectively with proper optimization and infrastructure.
  • It is crucial to continuously monitor performance metrics and optimize rules and infrastructure as needed.

Best Practices:

  • Performance Testing: Conduct performance testing in a staging environment that mirrors the production setup to understand the impact of adding new rules.
  • Incremental Rollout: Introduce rules incrementally rather than all at once to monitor the impact on performance.
  • Regular Audits: Periodically audit and refine rules to ensure they are still relevant and optimized.
  • Monitoring Tools: Use monitoring tools to track system performance, identify bottlenecks, and adjust resources as necessary.

Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.