performance issues with 9.5.0-P1

[Fr34k]

Hello,
For 9.5.x, is the max-cache-size default 32M or 64M?
The FAQ for the non-programmer says:
Cache cleaning 
We have added two cache cleaning changes. One of these affects all cache users, while another affects users with caches that hit their configured memory limits. We have added a default cache size. Previously this was set to '0' which means unlimited; it is now set to 64 MB by default. This value was chosen somewhat by committee, and should be sufficient for most uses. This can be changed with the max-cache-size options statement. 
The  BIND 9 ARM says:
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 32M. 


----- Original Message ----
From: JINMEI Tatuya / 神明達哉 <Jinmei_Tatuya at isc.org>
To: Jim Gogan <gogan at email.unc.edu>
Cc: bind-users at isc.org
Sent: Monday, July 14, 2008 2:13:58 PM
Subject: Re: performance issues with 9.5.0-P1

At Mon, 14 Jul 2008 12:48:43 -0400,
Jim Gogan <gogan at email.unc.edu> wrote:

> Wondering if anyone else has encountered what I would consider 
> significant performance issues with BIND 9.5.0-P1.  On three different 
> Solaris systems, each one averaging about 270-280 queries per second, 
> since the patch install, the load average has gone from acceptable to 
> not-so-much (now averaging between 2-4) with named hitting between 
> 49-90% of the CPU.
> 
> Just curious to see if anyone else is seeing this or if it's just us.

If you have upgraded from 9.4 or 9.3 (or even older) to 9.5.0-P1,
please check your max-cache-size value.  9.5 has a pretty small
default value (32MB) for middle-to-large scale caching servers, and it
can make the server unnecessarily heavy-load.

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.