Too many open files (not only BIND 9.5.0-P1)

[Shumon Huque]

On Fri, Jul 11, 2008 at 03:03:19PM -0700, JINMEI Tatuya / ?$B?@L at C#:H?(B wrote:
> 
> If named needs more than 1024 open sockets simultaneously, I really
> recommend beta versions.  With that number of open sockets, the API
> overhead of P1s will be too severe anyway, even if it doesn't cause
> 'too many open files'.

Another quick report:

I upgraded my campus primary resolver to 9.4.2-P1 (with the default 
Solaris 10 FD_SETSIZE of 1024). No changes were made to the config
file.

So far, it's been mostly fine. This is the busiest resolver on my 
campus. Not gigantic by most measures, but fairly busy - it does 
about 1,500 queries/second. Hardware is a Sun T2000 server (8-core 
Ultra-T1 1.2GHz CPU).

I saw a rash of 5 "too many open files" messages right immediately 
after startup. I assumed that was when named momentarily exceeded 1024
descriptors. Since then, I've seen it only once more. Interrogating
the number of open files via /proc periodically, I've seen it as
high as 930. So, I'm likely planning to install 9.4.3b2 with a 
bumped up FD_SETSIZE to obtain more headroom.

Memory consumption is only upto 300MB. It usually grows to 750 or
800MB as the cache builds up (my max-cache-size is 1024MB). And I 
assume that growth might have a net positive effect on the outbound 
query port consumption rate. CPU usage has increased somewhat from
7% to 10%.

--Shumon.