[Pdns-users] Performance?

Dan Durrer dan at vitalwerks.com
Tue Apr 8 22:14:53 UTC 2003


Cool.. That would work.. Our thought was to have a script that runs on
the each dns server.  Querying its database every 5 mins searching for
records w/ updated timestamps since its last run.. Then run pdnscontrol
on each of those newly changed hosts.  As our current system load is,
this would be roughly 1700 calls to pdnscontrol every 5 minutes. Our
user base is still rapidly growing.  Does anyone see any problems with
this keeping in mind scaling to many more updates per 5 min interval?

Thanks
Dan

-----Original Message-----
From: Mike Benoit [mailto:mikeb at netnation.com] 
Sent: Tuesday, April 08, 2003 3:07 PM
To: Dan Durrer
Cc: pdns-users at mailman.powerdns.com
Subject: RE: [Pdns-users] Performance?


We use a perl script and xinetd on each server, then simply echo some
commands to a specified port on each server.

On Tue, 2003-04-08 at 13:50, Dan Durrer wrote:
> Sorry for the delayed response.. In regards to pdns_control purge,  
> this is cool for the master server.  But it seems to me that we would 
> need to run this command on each server right?  How do you solve this 
> issue?
> 
> Dan
> 
> -----Original Message-----
> From: Mike Benoit [mailto:mikeb at netnation.com]
> Sent: Friday, April 04, 2003 12:17 PM
> To: Dan Durrer
> Cc: pdns-users at mailman.powerdns.com
> Subject: Re: [Pdns-users] Performance?
> 
> 
> With that many updates, make sure you use InnoDB table types. This 
> will give you row level locking, and probably the only way MySQL will 
> work for you. Alternatively use PostgreSQL, though it may be slightly 
> slower.
> 
> Uptime: 28.1 days Queries/second, 1, 5, 10 minute averages: 106, 102, 
> 102. Max queries/second: 950
> 
> Our nameservers are PIII-866's running PDNS, and PostgreSQL on the 
> same box, it handles spikes without much problem at all. The key of 
> course is in the caching values you set. We set our cache to timeout 
> after 1day, but to still get instant updates, we simply push cache 
> expiration commands to PDNS. (pdns_control purge www2.blah.com) This 
> gives you the best of both worlds and you should be able to scale PDNS

> well past thousands of queries/sec.
> 
> On Thu, 2003-04-03 at 15:26, Dan Durrer wrote:
> > Hello,
> > 
> > We are considering using PowerDNS for a service we offer.  Currently
> > we are using BIND 9.  My question is just how well does this
software 
> > perform under heavy load?  Are we going to run into MySQL
limitations?
> 
> > We heavily use the dynamic update feature of bind.  Processing 
> > roughly
> 
> > 300/updates a minute.  Our primary dns server answers about 480
> > queries/sec.  One big concern I have with BIND is that after it has 
> > been running for a few hours it can take up to 15 minutes to 
> > completely shut down, due to all the journal files that get synced.
> > 
> > Anyone out there care to share there experiences with powerDNS and 
> > it
> > ability to handle high traffic?  Additionally does MySQL replication

> > master/slave scenario use more or less bandwidth than a bind IXFR 
> > based system?
> > 
> > 
> > Thank you,
> > Dan
> > 
> > 
> > 
> > _______________________________________________
> > Pdns-users mailing list
> > Pdns-users at mailman.powerdns.com
> > http://mailman.powerdns.com/mailman/listinfo/pdns-users
-- 
Best Regards,
 
Mike Benoit
NetNation Communications Inc.
Systems Engineer
Tel: 604-684-6892 or 888-983-6600
 ---------------------------------------
 
 Disclaimer: Opinions expressed here are my own and not 
 necessarily those of my employer




More information about the Pdns-users mailing list