Hi Quanah,Thanks for replying, I have few more observation regrading my load runs, real time of load run with MDB is 98% even at 10 TPS.What version of OpenLDAP are you using?---2.4.32
What type of disk?
--root@tspatca2103> fdisk -l /dev/mapper/vg00-root
Disk /dev/mapper/vg00-root: 10.7 GB, 10737418240 bytes255 heads, 63 sectors/track, 1305 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytesSector size (logical/physical): 512 bytes / 512 bytesI/O size (minimum/optimal): 512 bytes / 512 bytesDisk identifier: 0x00000000
Disk /dev/mapper/vg00-root doesn't contain a valid partition tableroot@tspatca2103>
What type of file system?--ext4 (/dev/mapper/vg00-root on / type ext4 (rw,nouser_xattr))--/opt/openldap/yaju/sbin/slapadd -q -w -f /opt/openldap/yaju/etc/openldap/slapd.conf -l /root/yaju/db.ldif
What is your *exact* slapadd command?I am using jmeter to simulate the load.--
Thanks and Regards
On Tue, Aug 28, 2012 at 8:19 PM, Quanah Gibson-Mount <email@example.com> wrote:
--On Tuesday, August 28, 2012 5:29 PM +0530 Yajuvendra Singh <firstname.lastname@example.org> wrote:You don't provide any useful or relevant information, so it is impossible to help you.
Today we tried with to run the load with the below schema. We added about
.6M entries in the DB.
Still our performance is severely poor. (10 TPS)
Can anybody review our slapd.conf file and point us where we are wrong,
is there any other config we have missed out.
What version of OpenLDAP are you using?
What type of disk?
What type of file system?
What is your *exact* slapadd command?
There is virtually no tuning involved with MDB, although I strongly recommend you read Howard's notes about the writeback bits for EXT4 etc he made in a recent post to -technical about MDB.
Sr. Member of Technical Staff
A Division of VMware, Inc.
Zimbra :: the leader in open source messaging and collaboration