Your analysis only works if the requests are so evenly spaced throughout the day, that you don't end up with a bell curve (which is what you would end up with, actually). Imagine, that the default time to query for ntp would be 2AM localtime: For 2:00 Eastern (UTC-5) The poor server setup to field the requests would have to handle hundreds of thousands of requests all within a few minutes of each other: 500,000 * 100-byte request / (60 seconds / min * 5 min) = 166666bytes/sec = 1302kbps = 1.3Mbps.... This is of course assuming that the machine can handle all those requests: 100,000 / minute or 1.6k/s, which to my knowledge, would out-class all public ntp servers at the moment :) Of course, all numbers in this are just pulled out of the air :) -j On Tue, Aug 21, 2001 at 06:13:47PM +0100, Dom De Vitto wrote: > Hmmm, > 10,000,000 machines requesting one a day * 100-byte request > / 86400 seconds in a day = 11574 bytes/sec = 93kbits/second > I'm sure connexion could cope :) ---end quoted text--- -- Jason Legate Sr. Net/Sys Admin, eVine, Inc. work- jlegateat_private | home- jlegateat_private Key Fingerprint: 4FB4 2228 DE63 3BBA 7B72 40DD 13D5 2547 821D 2909
This archive was generated by hypermail 2b30 : Tue Aug 21 2001 - 21:54:27 PDT