#include <db.h>

int
DBENV->set_cachesize(DB_ENV *dbenv,
    u_int32_t gbytes, u_int32_t bytes, int ncache);

Description

Set the size of the database's shared memory buffer pool, i.e., the cache, to gbytes gigabytes plus bytes. The cache should be the size of the normal working data set of the application, with some small amount of additional memory for unusual situations. (Note, the working set is not the same as the number of simultaneously referenced pages, and should be quite a bit larger!)

The default cache size is 256KB, and may not be specified as less than 20KB. Any cache size less than 500MB is automatically increased by 25% to account for buffer pool overhead, cache sizes larger than 500MB are used as specified. For information on tuning the Berkeley DB cache size, see Selecting a cache size.

It is possible to specify caches to Berkeley DB that are large enough so that they cannot be allocated contiguously on some architectures, e.g., some releases of Solaris limit the amount of memory that may be allocated contiguously by a process. If ncache is 0 or 1, the cache will be allocated contiguously in memory. If it is greater than 1, the cache will be broken up into ncache equally sized separate pieces of memory.

The DBENV->set_cachesize interface may only be used to configure Berkeley DB before the DBENV->open interface is called.

The DBENV->set_cachesize function returns a non-zero error value on failure and 0 on success.

The database environment's cache size may also be set using the environment's DB_CONFIG file. The syntax of the entry in that file is a single line with the string "set_cachesize", one or more whitespace characters, and the three arguments specified to this interface, separated by whitespace characters, for example, "set_cachesize 1 500 2". Because the DB_CONFIG file is read when the database environment is opened, it will silently overrule configuration done before that time.

Errors

EINVAL

An invalid flag value or parameter was specified.

Called after DBENV->open was called.

The specified cache size was impossibly small.

See Also