<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D54z00006yQ0xnCACOkta Classic EngineIntegrationsAnswered2026-04-01T09:00:20.000Z2021-05-17T15:57:30.000Z2021-05-17T17:49:22.000Z

382es (382es) asked a question.

May 17, 2021 at 3:57 PM
Okta AD Agent requirements and usage

I had some questions regarding Okta’s AD agent. I realize the documentation lists minimum system requirements but I require more specific information regarding its CPU utilization and related metrics.

 

  • How much disk space does the Okta AD Agent use?
  • How much ram does it use (assume ten thousand users)?
  • What is it’s CPU utilization under load?

 

Any additional metrics you could provide me regarding its performance would be appreciated.

  • 2 answers
  • 1.01K views

  • k5fuw (k5fuw)

    • disk space - the agent binaries takes up ab out 5 MB, then assume another 50 MB or so of logs for every domain you register. We have three domains and our AD agent folder is currently at 153 MB. The logs automatically roll over so that figure has been pretty consistent for many years.
    • ram - number of users is irrelevant. the agent merely passes information between okta and AD, it doesn't store anything. It's been more than 3 weeks since our servers were patches and rebooted, so the agent's been running for that long and is currently consuming 75 MB of ram.
    • CPU utilization - our servers are monitored by SCOM and I've never had a peep out of them due to CPU performance. CPU utilization for the entire server rarely exceeds 10%, with the AD, RADIUS and On-Prem MFA agents running. However, we have four servers configured this way - two on-premises and two in AWS, so they are all sharing the load. We did run with just the two on-premises servers for the first couple of years, with no issues. The AWS servers were added later, for fault tolerance.
    Expand Post
    Selected as Best

  • k5fuw (k5fuw)

    • disk space - the agent binaries takes up ab out 5 MB, then assume another 50 MB or so of logs for every domain you register. We have three domains and our AD agent folder is currently at 153 MB. The logs automatically roll over so that figure has been pretty consistent for many years.
    • ram - number of users is irrelevant. the agent merely passes information between okta and AD, it doesn't store anything. It's been more than 3 weeks since our servers were patches and rebooted, so the agent's been running for that long and is currently consuming 75 MB of ram.
    • CPU utilization - our servers are monitored by SCOM and I've never had a peep out of them due to CPU performance. CPU utilization for the entire server rarely exceeds 10%, with the AD, RADIUS and On-Prem MFA agents running. However, we have four servers configured this way - two on-premises and two in AWS, so they are all sharing the load. We did run with just the two on-premises servers for the first couple of years, with no issues. The AWS servers were added later, for fault tolerance.
    Expand Post
    Selected as Best
This question is closed.
Loading
Okta AD Agent requirements and usage