Hi Nico,

On 06/19/2018 10:42 PM, Nico wrote:
> We upgraded to 1.3, everything fine.
> Redid our test with the following results:
> # procs       # listeners     kq/s
> <http://tornado.pert.com.ar/twiki/bin/view/FAQ/PersonalDnsDistPruebasCarga?sortcol=2;table=1;up=0#sorted_table>
> % no error
> <http://tornado.pert.com.ar/twiki/bin/view/FAQ/PersonalDnsDistPruebasCarga?sortcol=3;table=1;up=0#sorted_table>
> 1     6       340     94%
> 1     9       380     98%
> 1     15      400     100%
> 1     15      500     99%
> 1     25      600     98%
> 3     6       500     99%
> 
> 
> Above 550 Kqps we were over 85% of interface usage and were many network
> errors.

Thanks a lot for these numbers! It does look a lot better than last time.

> One important thing we noticed is that in our production configuration
> we have ~60 drop rules :
> addAction('example.com <http://example.com>', DropAction())
> 
> Whit these rules the performance dropped almost 30%
> We are moving those rules to the backend resolvers now, because it
> doesn't make sense
> to have this drop on performance when almost all our queries are cached
> (98% hit rate)

Did you consider grouping all those 60 rules into a single one using
SuffixMatchNodeRule()? The cost should be much lighter.


Best regards,
-- 
Remi Gacogne
PowerDNS.COM BV - https://www.powerdns.com/

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
dnsdist mailing list
dnsdist@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/dnsdist

Reply via email to