Library Version 12.1.6.0

DB_ENV->set_lk_partitions()
Prev | Chapter 6. The DB_LOCK Handle | Next

## DB_ENV->set_lk_partitions()

    #include <db.h>

    int
    DB_ENV->set_lk_partitions(DB_ENV *dbenv, u_int32_t partitions);

Set the number of lock table partitions in the Berkeley DB environment. The default value is 10 times the number of CPUs on the system if there is more than one CPU. Increasing the number of partitions can provide for greater throughput on a system with multiple CPUs and more than one thread contending for the lock manager. On single processor systems more than one partition may increase the overhead of the lock manager. Systems often report threading contexts as CPUs. If your system does this, set the number of partitions to 1 to get optimal performance.

The database environment's number of partitions may also be configured using the environment's DB_CONFIG file. The syntax of the entry in that file is a single line with the string "set_lk_partitions", one or more whitespace characters, and the number of partitions. Because the DB_CONFIG file is read when the database environment is opened, it will silently overrule configuration done before that time.

The `DB_ENV->set_lk_partitions()` method configures a database environment, not only operations performed using the specified DB_ENV handle.

The `DB_ENV->set_lk_partitions()` method may not be called after the DB_ENV->open() method is called. If the database environment already exists when DB_ENV->open() is called, the information specified to `DB_ENV->set_lk_partitions()` will be ignored.

The `DB_ENV->set_lk_partitions()` method returns a non-zero error value on failure and 0 on success.

### Parameters

#### partitions

The partitions parameter is the number of partitions to be configured in the Berkeley DB environment.

### Errors

The `DB_ENV->set_lk_partitions()` method may fail and return one of the following non-zero errors:

#### EINVAL

If the method was called after DB_ENV->open() was called; or if an invalid flag value or parameter was specified.

### Class

DB_ENV, DB_LOCK

### See Also

Locking Subsystem and Related Methods

Prev | Up | Next
DB_ENV->set_lk_max_objects() | Home | DB_ENV->set_lk_priority()