From: Bert Hubert Date: Thu, 14 Jul 2005 18:03:16 +0000 (+0000) Subject: docs X-Git-Tag: pdns-2.9.18~6 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d3fa6582802082a5bd4621a5ed113bc7bcc18be7;p=thirdparty%2Fpdns.git docs git-svn-id: svn://svn.powerdns.com/pdns/trunk/pdns@443 d19b8d6e-7fed-0310-83ef-9ca221ded41b --- diff --git a/pdns/docs/pdns.sgml b/pdns/docs/pdns.sgml index bf503a9dac..b050e15ee9 100644 --- a/pdns/docs/pdns.sgml +++ b/pdns/docs/pdns.sgml @@ -83,17 +83,21 @@ Version 2.9.18 (unreleased) - The '8 million domains' release, which also marks the battle readiness of the PowerDNS Recursor. This release brings a number of new features, + The '8 million domains' release, which also marks the battle readiness of the PowerDNS Recursor. The latest improvements have been made possible + by financial support and contributions by Register.com and + xs4all. Thanks! + + + This release brings a number of new features, but also has a new build dependency, the Boost library. Currently several big ISPs are evaluating the PowerDNS recursor for their resolving needs, some of them have switched already. - In the course of testing, over 350 million actual queries have been recorded and replayed, the answers turn out to be satisfactorily, - although we are still looking into some very minor discrepancies (less than 0.05% of queries have unexplained differences). + In the course of testing, over 350 million actual queries have been recorded and replayed, the answers turn out to be satisfactorily. This testing has verified that the pdns recursor, as shipped in this release, can stand up to heavy duty ISP loads - (over 20000 queries/second) and in fact does so better than major other nameservers. + (over 20000 queries/second) and in fact does so better than major other nameservers, giving more complete, being faster to boot. We invite ISPs who note recursor problems to record their problematic traffic and replay it using the tools described in @@ -220,6 +224,11 @@ the pdns recursor is among the faststest around. + + + Under high loads, or when unlucky, some query mthreads would get 'stuck', and show up in the statistics as eternally running queries. + + Lots of redundant gettimeofday() and time() calls were removed, which has resulted in a measurable speedup.