[Pdns-users] New recursor install, 50% timeout on first run

[Ciro Iriarte]

2014-10-13 10:37 GMT-03:00 bert hubert <bert.hubert at netherlabs.nl>:
> On Mon, Oct 13, 2014 at 10:10:43AM -0300, Ciro Iriarte wrote:
>> Hi!, I'm running some quick tests on a new Recursor (3.6.1) and I see
>> ~ 50% query timeouts. It has a good Internet connection but no clients
>> yet, can this be caused by empty cache?.
>
> Yes, on a cold cache, nameservers are a lot slower.
>
> You can improve on this by increasing the number of mthreads (max-mthreads)
> and the number of file descriptors.
>
> The best performance comes from a busy nameserver, as outlined on
> http://blog.netherlabs.nl/test/
>
> That your second time results were worse is weird, can you do a test with
> more than 1000 domains, say, 50000?
>
> Can you report "rec_control get-all" before and after a run?
>
> Perhaps your PowerDNS server is behind NAT and your other server isn't?
>
>         Bert

Hi Bert!, I've run again 1000 domain test with logging disabled (just
in case). The results look pretty much the same:
http://pastebin.com/Nsjhjnx3

Tried a cold cache with 80k domains, it was a disaster, I couldn't let
it finish.

The configuration:
----
local-address=<ip1>,<ip2>,<ip3>
allow-from=<test1>,<test2>,<test3>
threads=10
---

I'll double check with the networking guys, This server will use a
secondary public IP, but I see that the queries get out with the base
private IP, so it's possible that the edge NAT is causing this.


I'll keep you updated. Thanks!

-- 
Ciro Iriarte
http://iriarte.it
--