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

Re: Database access to .gdbm files

To: "Fox Flanders" <lds0062@cdc.net>, <openldap-software@OpenLDAP.org>
Subject: Re: Database access to .gdbm files
From: Peter Marschall <peter@adpm.de>
Date: Wed, 22 Oct 2003 22:15:06 +0200
Content-disposition: inline
In-reply-to: <004401c398d0$99290e10$7c640f0a@mfc.corp.mckee.com>
Organization: ADPM
References: <AIEGKPNFJLJIKKDJEFGFKEIKCDAA.tglemser@tele-consulting.com> <004401c398d0$99290e10$7c640f0a@mfc.corp.mckee.com>
User-agent: KMail/1.5.1

Hi,

On Wednesday 22 October 2003 21:13, Fox Flanders wrote:
> When doing an LDAP query (cn=*) to return all 14,000 of my users, it takes
> 1 minute 40 seconds using perl-ldap.  This to me seems very slow compared
> to the time it would take a database to do the same query.  I have very
> generous cache sizes, large enough to place the whole thing in memory.

Did you cross-check with the ldapsearch command that came with OpenLDAP ?
It might be a perl-ldap issue. AFAIK perl-ldap is pure Perl which sometimes 
may be slower than compiled C code.

Peter

-- 
Peter Marschall
eMail: peter@adpm.de

Follow-Ups:
- Re: Database access to .gdbm files
  - From: Peter Marschall <peter@adpm.de>

References:
- Convert Certificates LDAP-compatible without "LDIF"-Command
  - From: "Tobias Glemser" <tglemser@tele-consulting.com>
- Database access to .gdbm files
  - From: "Fox Flanders" <lds0062@cdc.net>

Prev by Date: Re: [openldap 2.1.12] add a new index in database
Next by Date: MySQL Backend for integration with existing setup
Index(es):
- Chronological
- Thread