Estimating the best ASCI: best practice

To improve the ePO - On-prem server performance, you might need to adjust the ASCI setting for your managed network.

To determine whether to change your ASCI, ask how often changes occur to endpoint policies on your ePO - On-prem server. For most organizations, once your policies are in place, they don't often change. Some organizations change an endpoint policy less frequently than once every few months. That means a system calling in every 60 minutes looking for a policy change, about eight times in a typical work day, might be excessive. If the agent does not find any new policies to download, it waits until the next agent-server communication, then checks again at its next scheduled check-in time.

To estimate the ASCI, your concern is not wasting bandwidth because agent-server communications are only a few kilobytes per communication. The concern is the strain put on the ePO - On-prem server with every communication from every agent in larger environments. All your agents need at least two communications a day with the ePO - On-prem server. This requires a 180–240 minute ASCI in most organizations.

For organizations with fewer than 10,000 nodes, the default ASCI setting is not a concern at 60 minutes. But for organizations with more than 10,000 nodes, change the default setting of 60 minutes setting to about 3–4 hours.

For organizations with more than 60,000 nodes, the ASCI setting is much more important. If your ePO - On-prem server is not having performance issues, you can use the 4-hour ASCI interval. If there are any performance issues, consider increasing your ASCI to 6 hours; possibly even longer. This change significantly reduces the number of agents that are simultaneously connecting to the ePO - On-prem server and improves the server performance.

Note

You can determine how many connections are being made to your ePO - On-prem server by using the ePO - On-prem Performance Counters.

This table lists basic ASCI guidelines.