-----Original Message----- From: Chris Hastie <[EMAIL PROTECTED]> To: [email protected] Date: Fri, 26 Aug 2005 16:52:46 +0100 Subject: Re: [time] Pool server/network loads
> On Thu, 25 Aug 2005, Brad Knowles <[EMAIL PROTECTED]> wrote: > > > > > The real solution for this problem is to use a database back-end, > > and have monitoring data update the database information in near > > real-time. You could also distribute that database information from > > the "master" server to the "slaves" via standard database techniques. > > You might be able to put something together with BIND and the > > DLZ-BIND stuff, but I think you're probably better off with something > > like PowerDNS. > > I haven't looked hard at PowerDNS, but one of the advantages of > BIND-DLZ is that > it is pretty damn flexible about the database schema and queries used. I run PowerDNS with the MySQL backend on several of my nameservers, you can change the queries it used to talk with the backend in the conf file, and as long as it gets the fields back in the order it's expecting, you can do pretty much whatever with the query. > It seems to me the main advantage here would be that a given nameserver > could > return a different set of results for each query, thereby hopefully > evening out > the spikes a bit. I don't know how random an ORDER BY RAND() really is, > but it > would be worth looking at. With MySQL at least, the randomness isn't perfect, but it is probalby good enough for our purposes. It also doesn't optimize at all (it uses a temporary table and a filesort, though it's still pretty quick.) I haven't looked into other RDBMs, though. _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
