On 5/17/07, Alica CCS <[EMAIL PROTECTED]> wrote: > All these global pool take over half of traffic. And you know the current > global pool is not geographically optimized. People querying the global > pool may get a distant server and inaccurate time (maybe error of a sec?) > Shouldn't the project do something to correct this? Like IP-based zone > view for different countries. (the Akamai way)
This has been tested on a small scale for the pool. The problem is you are trading widely distributed network resources for a high CPU and bandwidth load on the DNS servers. There is also the issue of geographically distributing the database containing pool members and monitoring to make sure they are available and accurate. Multi-master replication in databases is non-trivial to set up and maintain. Akamai can afford this, but can a volunteer project do the same? _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
