Hi Jinmei, Is there any change if you build named with/without threads (and with [EMAIL PROTECTED])? --> have yet to try this. Will test and let you know.
How many queries per second is that server normally accepting? --> we're seing about 4.2k - 5.5k requests per second. What's the normal cache hit rate (you can identify it via rndc stats outputs)? --> cache hit rate now is around 81.78% [View: _bind] ++ Name Server Statistics ++ 143899333 IPv4 requests received 233430 requests with EDNS(0) received 21771 TCP requests received 139685462 responses sent 17432 truncated responses sent 232697 responses with EDNS(0) sent 109402680 queries resulted in successful answer 552551 queries resulted in authoritative answer 135544531 queries resulted in non authoritative answer 35645 queries resulted in referral answer 4822525 queries resulted in nxrrset 2664657 queries resulted in SERVFAIL 21729984 queries resulted in NXDOMAIN 26211438 queries caused recursion 2087260 duplicate queries received 1732509 queries dropped ----- Original Message ----- From: "JINMEI Tatuya / ????" <[EMAIL PROTECTED]> To: "Elias" <[EMAIL PROTECTED]> Cc: <bind-users@isc.org> Sent: Thursday, August 07, 2008 12:31 AM Subject: Re: Issues with BIND 9.5.0-P2 > At Wed, 6 Aug 2008 16:38:43 +0800, > "Elias" <[EMAIL PROTECTED]> wrote: > >> I'm not sure if this is how we check for the number of sockets >> opened, but I'm seing over 4000. The number of recursive clients >> will also increase when using the P2 release (it was between 700-900 >> when running 9.5.1b1). > > Hmm, these are not a direct evidence, but it seems the server really > has a very many number of open UDP sockets. I don't think it matters > much, but just in case, is there any change if you build named > with/without threads (and with [EMAIL PROTECTED])? > > I'd like to know some other information that may matter: > - How many queries per second is that server normally accepting? > - What's the normal cache hit rate (you can identify it via rndc stats > outputs)? > > --- > JINMEI, Tatuya > Internet Systems Consortium, Inc. >