lookup timeouts

Barry Margolin barmar at bbnplanet.com
Fri Jan 21 15:40:27 UTC 2000


In article <200001210923.KAA02301 at mail.emit.pl>,
Ian Carr-de Avelon  <avelon at emit.pl> wrote:
>I also have, and have reported to this list, a problem of authoratitive 
>lookups becoming slow and then timing out. It was suggested to me that
>named needs almost zero swaping. (although I don't see why it should 
>start to have a latency of seconds when no other deamon on the system
>has)

Because named has incredibly poor memory management.  Query processing
tends to touch lots of pages of the cache memory, with not much locality.
So if the cache isn't all in RAM, it will tend to thrash.

Most other daemons have small working sets, so they aren't as bothered by
paging.

-- 
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.



More information about the bind-users mailing list