Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 6199 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Client update maximum / throttling

ttl
We have a large number of VMs that are apparently checking for and updating at the same time. This is causing massive disk latency and slowness on a large number of systems (I/O storm). Is there some way we can limit the number of systems that can update at once?
:46731


This thread was automatically locked due to age.
  • 0

    Hello ttl,

    are these desktops, how many (per host) and are even the minor (IDE) updates an issue or only the major ones?

    Endpoints are independent (from each other and the management server) and check for updates at regular intervals, increasing the interval might spread the load but you don't have control over the exact times (or the number of endpoints). 

    Christian

    :46749
  • 0
    As I've mentioned, these are VMs (Virtual Machines). They're workstation VMs. How would I know if they're minor or major updates causing the issue, considering that the symptoms are that a large number of people suddenly get unresponsive VMs and the main process eating CPU and Disk I/O is SAVservice.exe ?
    :46933
  • 0

    Hello ttl,

    update checks are at the specified interval, minor updates several times a day and major updates roughly each month. This should correspond to the frequency of the symptoms. SAVService.exe restarts after an update but I'm not sure if this would result in excess resource usage. But maybe you can correlate the issue with the update times in the autoupdate logs?

    Christian

    :46935