Список проголосовавших за комментарий "<a href="/r.php?u=http%3A%2F%2Fluka.manojlovic.net%2F2011%2F12%2F18%2Fchange-time-sync-interval-in-windows-server-2008-r2%2Fcomment-page-1%2F%23comment-116738&s=1283145602" target="_blank">Интересно</a><br/> <blockquote><br/> <p>Instead of setting an interval of 3600 seconds (1 hour exactly), it might be better to set an interval that’s a prime number, like 3607 seconds. If you are querying the server every hour, and others are doing the same, then every so often the server will experience a high number of queries. But if your query interval is a prime number, then it will almost never overlap with the people sending queries every 3600 seconds (it will only overlap once every 3607 queries), so the load on the server will be more “smooth” instead of having bursts of high load.</p><br/> <p>This is a good general rule, in fact. If you’re setting up *any* repeating task, intervals that are prime numbers are usually better than intervals that are multiples of an hour, or a day, or a week. Or if you must have intervals that are whole days (for example, the backups must be run every night), then pick an “unusual” time like 03:19 instead of 03:00. Again, you’ll be less likely to overlap with other “run this every day” tasks, and cause more “smooth” load on the server(s).</p><br/> </blockquote>"