Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 6198 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.
Parents
  • 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
Reply
  • 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
Children
No Data