IAM Performance
IAM performance measures how long an identity service takes to produce the expected outcome, indicator by indicator.
- Synonym
- IAM response time
Definition
IAM performance is not a single number: it depends on the capability concerned. Typical measures include user-perceived authentication time, the latency of a runtime authorization decision, directory synchronisation duration, the delay between an HR event and access actually becoming available, the runtime of a review campaign, or event processing throughput. Each of these has its own expectations and technical constraints, and comparing them to each other makes little sense. Performance is therefore defined against the expected service, distinguishing synchronous processing that blocks a user journey from asynchronous processing that can legitimately take longer.
Why it matters
Poorly framed performance expectations either oversize a platform or degrade an authentication experience people go through every day.
The Ariovis perspective
There is no single IAM performance indicator. A runtime authorization decision may need a few milliseconds, while asynchronous provisioning can legitimately take longer. Performance must be measured against the expected service, not in the absolute.
Related services
Common pitfalls
- A common mistake is applying a single response-time target to processes of fundamentally different natures.
Resources
Explore this category
These concepts matter most inside a real project.
The first conversation helps establish your context, the systems involved and the next useful decision.