Berkeley DB Reference Guide: Configuring locking

Berkeley DB Reference Guide:
Locking Subsystem

Configuring locking

The DB_ENV->set_lk_detect method specifies that the deadlock detector should be run whenever a lock is about to block. This option provides for rapid detection of deadlocks at the expense of potentially frequent invocations of the deadlock detector. On a fast processor with a highly contentious application where response time is critical, this is a good choice. An option argument to the DB_ENV->set_lk_detect method indicates which lock requests should be rejected.

(DB_ENV->set_lk_detect 는 데드락 디텍터를 설정한다.이 옵션은 빠른 데드락 탐지를 제공한다.)

In general, when applications are not specifying lock and transaction timeout values, the DB_LOCK_DEFAULT option is probably the correct first choice, and other options should only be selected based on evidence that they improve transaction throughput. If an application has long-running transactions, DB_LOCK_YOUNGEST will guarantee that transactions eventually complete, but it may do so at the expense of a large number of lock request rejections (and therefore, transaction aborts).

(일반적으로, 락과 트랜젝션 타임아웃값이 설정되지 않을때 DB_LOCK_DEFAULT옵션이 첫번째 선택할수 있는 것이다.다른 옵션은 트랜젝션 처리향상을 확신할때 선택될 수 있다.만약 애플리케이션이 long-running트랜젝션을 가질때 DB_LOCK_YOUNGEST은 트랜젝션의 마침을 보증한다.그러나 이것은 많은 락 요청을 거부하고 (역자추가:요청쓰레드의)트랜젝션을 취소시킴으로 비용이 높다.)

The alternative to using the DB_ENV->set_lk_detect method is to explicitly perform deadlock detection using the Berkeley DB DB_ENV->lock_detect method.

( DB_ENV->set_lk_detect사용에 대한 대안은 버클리디비의 DB_ENV->lock_detect 를 사용하는것이다.)

The DB_ENV->set_lk_conflicts method allows you to specify your own locking conflicts matrix. This is an advanced configuration option, and is almost never necessary.

(DB_ENV->set_lk_conflicts 은 사용자 락 충돌 매트릭스를 설정한다.이것은 거의 쓰지 않고 고급 설정옵션이다.)

Berkeley DB Reference Guide:Locking Subsystem

Configuring locking

Berkeley DB Reference Guide:
Locking Subsystem