Berkeley DB: DBENV->set_mp_mmapsize
Description: Berkeley DB: An embedded database programmatic toolkit.
Keywords: embedded,database,programmatic,toolkit,b+tree,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,java,C,C++

# DBENV->set_mp_mmapsize |

`

###

    #include <db.h>

    int
    DBENV->set_mp_mmapsize(DB_ENV *dbenv, size_t mp_mmapsize);

# Description

Files that are opened read-only in the pool (and that satisfy a few other criteria) are, by default, mapped into the process address space instead of being copied into the local cache. This can result in better-than-usual performance, as available virtual memory is normally much larger than the local cache, and page faults are faster than page copying on many systems. However, in the presence of limited virtual memory it can cause resource starvation, and in the presence of large databases, it can result in immense process sizes.

Set the maximum file size, in bytes, for a file to be mapped into the process address space. If no value is specified, it defaults to 10MB.

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

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

The environment's maximum mapped file 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_mp_mmapsize", one or more whitespace characters, and the size in bytes. Configuration in the DB_CONFIG file silently overrules configuration done using the DBENV->set_mp_mmapsize function.

# Errors

EINVAL
  An invalid flag value or parameter was specified.

  Called after DBENV->open was called.

# See Also

DBENV->set_mp_mmapsize, memp_fclose, memp_fget, memp_fopen, memp_fput, memp_fset, memp_fsync, memp_register, memp_stat, memp_sync and memp_trickle.`

Copyright Sleepycat Software