[time] GPS Time Server Survey

Chris Kuethe chris.kuethe
Fri Apr 25 18:41:22 UTC 2008


well if your hardware/ip stack can handle 300pps, I'm going to
handwave and say you can handle 100 qps (gotta save some time for
timekeeping, ntpd, ssh, etc.), or 360000qph
100 very rude clients polling at 1Hz
90000 very polite clients polling once every 15minutes (~1.1e-3 Hz)

and i'll have to go through my logs to give you a frequency
distribution. don't forget bursty clients too.

CK

On Fri, Apr 25, 2008 at 11:21 AM, Kipton Moravec <kip at kdream.com> wrote:
> So an wild estimate would be 300 packets a second.
>
>  How many NTP users would that translate to realistically?
>
>  Kip
>
>
>  On Fri, 2008-04-25 at 10:04 -0700, Ask Bj?rn Hansen wrote:
>  > On Apr 25, 2008, at 9:52, Kipton Moravec wrote:
>  >
>  > > It may be comparable to an 80 MHz 486 processor. What is the best
>  > > guess
>  > > for that system to serve time?
>  >
>  >
>  > A 133Mhz 486-ish thing (Soekris 4501) stopped at about 500 packets a
>  > second IIRC.
>  >
>  >
>  >    - ask
>  >
>  --
>
> Kipton Moravec KE5NGX
>  "Always do right; this will gratify some people and astonish the rest."
>  --Mark Twain
>
>
>  _______________________________________________
>
>
> timekeepers mailing list
>  timekeepers at fortytwo.ch
>  https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
>



-- 
GDB has a 'break' feature; why doesn't it have 'fix' too?



More information about the pool mailing list