--On Thursday, September 05, 2013 10:58 PM +0300 Покотиленко Костик casper@meteor.dp.ua wrote:
В Чтв, 05/09/2013 в 11:35 -0700, Quanah Gibson-Mount пишет:
--On Thursday, September 05, 2013 9:05 PM +0300 Покотиленко Костик casper@meteor.dp.ua wrote:
Hi,
Is there a way to log the time each operation took?
I have strange CPU load (~200%) with just ~15 operations per second. SRCH is >90% of all operations. All attributed involved in search a indexed (many single attribute indexes, ~30).
The point is to find which search operations a taking long time to develop a solution.
OS? OpenLDAP version? OpenLDAP Backend? Do you see any issues in I/O wait? Size of database? Number of entries in database? etc. Provide some relevant information.
OS: Ubuntu 12.04.2 LTS Slapd: 2.4.28-1.1ubuntu4.3
Ugh, ancient.
Backend: HDB
Yuck.
FULL database ldif size: 2M /var/lib/ldap size: 220Mb (190Mb of which are 19 log.* files) Database entries: 1,7k
Well, that is pretty tiny. So not likely to be a configuration issue.
Could be some of what was fixed in 2.4.32: Fixed slapd-bdb/hdb cache hang under high load (ITS#7222) or 2.4.31: Fixed slapd-bdb/hdb idlcache with only one element (ITS#7231)
personally, I would highly advise upgrading to a current release (2.4.36) and switching to back-mdb.
--Quanah
--
Quanah Gibson-Mount Lead Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration