Performance issues with deadwood

Juergen Daubert juergen.daubert at t-online.de
Tue Sep 7 06:56:00 EDT 2010


On Mon, Sep 06, 2010 at 08:47:07PM -0700, Sam Trenholme wrote:
> > $:> time $(for h in $(cat hosts.txt); do printf "\n\n\n"; dig $h; done > test.log)
> >
> > The result is rather disappointing, the mean value over several runs
> > is around
> >
> >  8 min for deadwood and
> >  1 min for unbound.
> 
> OK, I’ve found and fixed a bug in Deadwood which accounted for about
> two thirds of the slowdown compared to unbound.
> 
> I just did the same test you did, and this the timings I saw:
> 
> * 7 minutes 29 seconds without the bug patched (about the same you
> saw, with a fairly large cache in place)
> 
> * 2 minutes 57 seconds with the bug patched (from a “cold start”: No cache)

Yeah, it's much  better now :) 

I've done 5 measurements after a cold start and got values in the range 
of 1 min 40 sec and 2 min 49 sec with a mean value of 2 min 15 sec. 
We have fewer time-outs as well now, range between 0 and 5, 1.6 mean.


-- 
Juergen Daubert  |  mailto:jue at jue.li  
Korb, Germany    |  http://jue.li/crux



More information about the list mailing list