[Date Prev][Date Next] [Chronological] [Thread] [Top]

simpler lockobj for back-bdb entry cache locking

To: openldap-devel@OpenLDAP.org
Subject: simpler lockobj for back-bdb entry cache locking
From: Jonghyuk Choi <jongchoi@us.ibm.com>
Date: Thu, 10 Apr 2003 23:14:27 -0400
Cc: hyc@highlandsun.com
Importance: Normal
Sensitivity:




When lockobj is changed from e_nname to e_id,
1% of db overhead is cut down from the execution trace
(ftp://ftp.openldap.org/incoming/profile3.txt)
and DirMark is up to 2381.2 ops/sec.
The hashing function of BerkeleyDB seems performance sensitive
to the key length. (__lock_ohash and __ham_func5)

- Jong
------------------------
Jong Hyuk Choi
IBM Thomas J. Watson Research Center - Enterprise Linux Group
P. O. Box 218, Yorktown Heights, NY 10598
email: jongchoi@us.ibm.com
(phone) 914-945-3979    (fax) 914-945-4425   TL: 862-3979

Follow-Ups:
- RE: simpler lockobj for back-bdb entry cache locking
  - From: "Howard Chu" <hyc@highlandsun.com>

Prev by Date: RE: Thread-local malloc discussion summary
Next by Date: RE: Thread-local malloc discussion summary
Index(es):
- Chronological
- Thread