19 Bře
2013
19 Bře
'13
14:08
Hi Johan,
this is a questionable attempt to prevent thundering herd problem
before a real fix is implemented,
as mentioned in other thread. But perhaps this was set too
aggressively, I have set it to ~ 4k q/s in the release branch again,
this should be acceptable for the time being (until 1.3).
Cheers,
Marek
On 18 March 2013 19:59, <jh(a)netriplex.com> wrote:
Hello,
Yesterday I had Knot 1.1.0 installed and with 4000 test zones on a slave
server configuration, a knotc refresh would hit my master to check SOA on
all zones very quickly (I would see over 600 queries per second). It could
generally complete the task in well under 60 seconds.
Today I have upgraded to 1.2.0-RC3 and with the same 4000 test zones on a
slave server configuration a knotc refresh is extremely slow. It issues SOA
queries to the master at about 10 queries per second.
Why this change? Is there any setting I can implement to speed this up? In a
production environment with 250k+ zones, this obviously won’t work.
Thanks!
Jonathan
_______________________________________________
knot-dns-users mailing list
knot-dns-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users