[Date Prev][Date Next]
Re: sanity check on updating from HDB backend to MDB
Brian Reichert wrote:
On Tue, Aug 12, 2014 at 03:47:10PM -0400, Christopher Wood wrote:
On Tue, Aug 12, 2014 at 03:22:57PM -0400, Brian Reichert wrote:
'top' still shows slapd only using %50, so I hazard that it keeps
to one CPU. Is that a valid assumption?
Try pressing "1" to have top show individual CPUs.
Yep, I know that trick. On my host, I see this:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
16278 root 20 0 44764 1888 1488 R 100.0 0.0 0:18.13 ldapsearch
15840 ldap 20 0 20.4g 4.3g 4.3g S 51.1 36.9 14:48.09 slapd
One could argue I should not be running a big query on the same
host as the server, but that is how I've been doing all of my recent
If ldapsearch is already running at 100% CPU then it's the limiting factor
here so no, you're not going to get any faster. I still find it a bit strange,
ldapsearch should still be faster than slapd. Do you have a non-OpenLDAP
ldapsearch installed on that machine? The FedoraDS/389DS/RHDS tools are
certainly slower, so that could make a difference.
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/