On Wed, Aug 13, 2014 at 11:34:46AM -0400, Brian Reichert wrote:
On Tue, Aug 12, 2014 at 06:59:52PM -0700, Howard Chu wrote:
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.
Good call; I'll review; I was using the ldapsearch from CentOS's RPM, not the one provided by the LTB project's RPM.
I'll report back.
Ok, just to report:
Using LTB's ldapsearch didn't improve things.
Running an ldapsearch remotely did allow slapd to take up 100% CPU, but the queries didn't complete any quicker. As I introduced network latency, I'm not shocked.
I feel that, for now, this is Good Enough.
There are other attributes of the MDB database I need to explore; resizing, backups, etc. Off I go!