9.2.3 max-cache-size is really unlimited?

[Mark Andrews]

	Looks like you have reached equilibrium.
	The default is 0, which is truely unlimited.
	"unlimited" gives you 4G.

> fbsd 4.10
> bind 9.2.3 caching-only
> approx 2+ million queries + createfetches/hour
> 2 GB RAM
> 
> named.conf has no max-cache-size sub-statement
> 
> named seems constantly stuck at memory size of:
> 
> PID USERNAME PRI NICE  SIZE    RES STATE    TIME   WCPU    CPU COMMAND
> 989 root       2   0 98856K 98256K select 218:39  1.12%  1.12% named
> 
> Stuck in the sense it stays at this number.
> 
> from ARM:
> 
> max-cache-size
> The maximum amount of memory to use for the server's cache, in bytes. When 
> the amount of data
> in the cache reaches this limit, the server will cause records to expire 
> prematurely so that the limit is
> not exceeded. In a server with multiple views, the limit applies separately 
> to the cache of each view.
> The default is unlimited, meaning that records are purged from the cache 
> only when their TTLs
> expire.
> 
> but it appears that the default is limited.  Confirmation?
> 
> thanks,
> Len
> 
> 
> 
> _____________________________________________________________________
> http://IMGate.MEIway.com : free anti-spam gateway, runs on 1000's of sites
> 
> 
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org