Generic reasons for recursive performance not to peg CPU?

Barry Margolin barmar at alum.mit.edu
Mon Jan 13 03:30:30 UTC 2014


In article <mailman.2014.1389579103.20661.bind-users at lists.isc.org>,
 Doug Barton <dougb at dougbarton.us> wrote:

> Thanks for the response, but you're answering a different question than 
> I asked. :)  The question I'm interested in is, "Why is the recursive 
> server not pegging the CPU?" I'm aware that there will be a difference 
> in qps between auth-only and recursive, but the recursive server seems 
> to be working a lot less hard than the auth server, and I can't figure 
> out why.

If the answer isn't already in cache, the server has to fire off the 
recursive query, and then doesn't have to do anything until the response 
arrives.

But an auth-only server doesn't spend any time waiting for responses.

-- 
Barry Margolin
Arlington, MA


More information about the bind-users mailing list