Edit File - File Manager

Edit File: max.html

<html>
<head>
<title>Berkeley DB Reference Guide: Configuring locking: sizing the system</title>
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
<meta name="keywords" content="embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++">
</head>
<body bgcolor=white>
<a name="2"></a>
<table width="100%"><tr valign=top>
<td><dl><dt>Berkeley DB Reference Guide:<dd>Locking Subsystem</dl></td>
<td align=right><a href="../lock/config.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../lock/stdmode.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
Configuring locking: sizing the system
The lock system is sized using the following four methods:
<blockquote><pre><a href="../../api_c/env_set_lk_max_locks.html">DB_ENV-&gt;set_lk_max_locks</a>
<a href="../../api_c/env_set_lk_max_lockers.html">DB_ENV-&gt;set_lk_max_lockers</a>
<a href="../../api_c/env_set_lk_max_objects.html">DB_ENV-&gt;set_lk_max_objects</a>
<a href="../../api_c/env_set_lk_partitions.html">DB_ENV-&gt;set_lk_partitions</a></pre></blockquote>
The <a href="../../api_c/env_set_lk_max_locks.html">DB_ENV-&gt;set_lk_max_locks</a>, <a href="../../api_c/env_set_lk_max_lockers.html">DB_ENV-&gt;set_lk_max_lockers</a>,
and <a href="../../api_c/env_set_lk_max_objects.html">DB_ENV-&gt;set_lk_max_objects</a> methods specify the maximum number of
locks, lockers, and locked objects supported by the lock subsystem,
respectively. The maximum number of locks is the number of locks that
can be simultaneously requested in the system. The maximum number of
lockers is the number of lockers that can simultaneously request locks
in the system. The maximum number of lock objects is the number of
objects that can simultaneously be locked in the system. Selecting
appropriate values requires an understanding of your application and its
databases. If the values are too small, requests for locks in an
application will fail. If the values are too large, the locking
subsystem will consume more resources than is necessary. It is better
to err in the direction of allocating too many locks, lockers, and
objects because increasing the number of locks does not require large
amounts of additional resources. The default values are 1000 of
each type of object.
The <a href="../../api_c/env_set_lk_partitions.html">DB_ENV-&gt;set_lk_partitions</a> method specifies the number of lock
table partitions. Each partition may be accessed independently by
a thread and more partitions can lead to higher levels of concurrency.
The default is to set the number of partitions to be 10 times the number
of cpus that the operating system reports at the time the environment is
created.
Having more than one partition when there is only one cpu is not beneficial and
the locking system is more efficient when there is a single partition.
Operating systems (Linux, Solaris) may report thread contexts as cpus and it
may be necessary to override the default to force a single partition on
a single hyperthreaded cpu system.
Objects and locks are divided among the partitions so it best to allocate
several locks and objects per partition. The system will force there
to be at least one per partition.
If a partition runs out of locks or objects it will steal what is needed
from the other partitions. This operation could impact performance if
it occurs too often.
When configuring a Berkeley DB Concurrent Data Store application, the number of lock objects needed
is two per open database (one for the database lock, and one for the
cursor lock when the <a href="../../api_c/env_set_flags.html#DB_CDB_ALLDB">DB_CDB_ALLDB</a> option is not specified). The
number of locks needed is one per open database handle plus one per
simultaneous cursor or non-cursor operation.
Configuring a Berkeley DB Transactional Data Store application is more complicated. The recommended
algorithm for selecting the maximum number of locks, lockers, and lock
objects is to run the application under stressful conditions and then
review the lock system's statistics to determine the maximum number of
locks, lockers, and lock objects that were used. Then, double these
values for safety. However, in some large applications, finer
granularity of control is necessary in order to minimize the size of the
Lock subsystem.
The maximum number of lockers can be estimated as follows:
<ul type=disc>
<li>If the database environment is using transactions, the maximum number
of lockers can be estimated by adding the number of simultaneously
active non-transactional cursors open database handles to the number of
simultaneously active transactions and child transactions (where a child
transaction is active until it commits or aborts, not until its parent
commits or aborts).
<li>If the database environment is not using transactions, the maximum
number of lockers can be estimated by adding the number of
simultaneously active non-transactional cursors and open database
handles to the number of simultaneous non-cursor operations.
</ul>
The maximum number of lock objects needed for a single database
operation can be estimated as follows:
<ul type=disc>
<li>For Btree and Recno access methods, you will need one lock object per
level of the database tree, at a minimum. (Unless keys are quite large
with respect to the page size, neither Recno nor Btree database trees
should ever be deeper than five levels.) Then, you will need one lock
object for each leaf page of the database tree that will be
simultaneously accessed.
<li>For the Queue access method, you will need one lock object per record
that is simultaneously accessed. To this, add one lock object per page
that will be simultaneously accessed. (Because the Queue access method
uses fixed-length records and the database page size is known, it is
possible to calculate the number of pages -- and, therefore, the lock
objects -- required.) Deleted records skipped by a <a href="../../api_c/dbc_get.html#DB_NEXT">DB_NEXT</a> or
<a href="../../api_c/dbc_get.html#DB_PREV">DB_PREV</a> operation do not require a separate lock object.
Further, if your application is using transactions, no database
operation will ever use more than three lock objects at any time.
<li>For the Hash access method, you only need a single lock object.
</ul>
For all access methods, you should then add an additional lock object
per database for the database's metadata page.
Note that transactions accumulate locks over the transaction lifetime,
and the lock objects required by a single transaction is the total lock
objects required by all of the database operations in the transaction.
However, a database page (or record, in the case of the Queue access
method), that is accessed multiple times within a transaction only
requires a single lock object for the entire transaction.
The maximum number of locks required by an application cannot be easily
estimated. It is possible to calculate a maximum number of locks by
multiplying the maximum number of lockers, times the maximum number of
lock objects, times two (two for the two possible lock modes for each
object, read and write). However, this is a pessimal value, and real
applications are unlikely to actually need that many locks. Reviewing
the Lock subsystem statistics is the best way to determine this value.
<table width="100%"><tr><td> </td><td align=right><a href="../lock/config.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../lock/stdmode.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
Copyright (c) 1996,2008 Oracle. All rights reserved.
</body>
</html>

Back to File Manager