|
Why is the Detection Interval set at 22 hours? |
| I imagine that the reason for 22 hours and not 24 hours, as
well as the fact that the detection interval is also minus 1%-20% of the
defined detection interval, is so that the patch transfers that take place
between the WUS server and the clients are spread around the clock, rather
than having all of your clients try to hit the server at the same time. Again, remember, WUS uses BITS. BITS is, by design, bandwidth-usage limited. If a number of clients simultaneously hit your WUS server, BITS will actually choke the bandwidth transfer to a percentage of the interface capability. The net effect is that bandwidth transfer per client is reduced, even if there is no other traffic on the network. It's more efficient to create a scenario where the number of simultaneous WUS client connections is minimized. By doing so, the WUS client is able to maximize throughput based on the WUS bandwidth available on the server interface, and spend less time overall transferring patch files. Thus, the net effect of setting the default to 22 hours is that eventually all sessions will be spread out around the clock, stabilizing and minimizing the load on the server, and maximizing the individual throughput to each client. |