Hi Lee,
In the past few months, quite some CNS servers have been replaced by the
PowerDNS Recursor, so you are not alone!
The 40,000 number has been reproduced by a number of separate parties,
sample output is below.
First, please read http://doc.powerdns.com/recursor-performance.html
First things first: use threads=4 or threads=8 and packet-cache.
This is how I did it:
Run a couple of dnsperf's like this:
./dnsperf -d queryfile-example-3million -s IP -p port -t 2 -l
$((3600*10)) -q 2000 -Q 2000 logfile.log 21
This will run a dnsperf from a queryfile for 10 hours (so you
Thanks for that information, Bert.
I had seen the documentation before... perhaps I should provide some more
information.
Here are the options I'm using at the moment (I've tried several values):
---
disable-packetcache=no
Looks like I've narrowed down the issue from this setup.
The issue was one of concurrency... by boosting it up to 4000 outstanding, I
was able to break over the 30,000 per second mark. It's quite possible that
some combination of settings means we need to run more concurrent queries to
reach
On Mon, May 17, 2010 at 03:23:21PM +0800, Lee Standen wrote:
Thanks for that information, Bert.
I had seen the documentation before... perhaps I should provide some more
information.
Here are the options I'm using at the moment (I've tried several values):
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I didn't read the whole thread. But we had the same problem in past. Is
it maybee a timeout mysql connection. We had this only system with out load.
Ciao
Marco
Am 06.05.10 07:45, schrieb bert hubert:
On Wed, May 05, 2010 at 11:27:13AM
Perf testing of 2/4/6/8 threads still shows optimal performance at 4
threads. Cache size of 3M, using test file of 3M addresses.
Tested on HP blades with quad-core X5570 CPU and 48GB RAM, 146GB 15k SAS
drives running on CentOS 5.x with a custom RPM.
2 threads:
new.2.1: Maximum throughput:
