OpenLDAP
Up to top level
Build   Contrib   Development   Documentation   Historical   Incoming   Software Bugs   Software Enhancements   Web  

Logged in as guest

Viewing Incoming/7514
Full headers

From: quanah@openldap.org
Subject: Optimize OpenLDAP with paged results
Compose comment
Download message
State:
0 replies:
0 followups:

Major security issue: yes  no

Notes:

Notification:


Date: Wed, 30 Jan 2013 21:34:35 +0000
From: quanah@openldap.org
To: openldap-its@OpenLDAP.org
Subject: Optimize OpenLDAP with paged results
Full_Name: Quanah Gibson-Mount
Version: 2.4.33
OS: Linux 2.6
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (74.196.25.250)


Currently, searches of back-mdb using paged results are extremely slow.  Up to
300 times slower than when not using paged results:

Without paged results:

 time  ldapsearch -LLL -x -H ldap://zre-ldap002.eng.vmware.com -b
"ou=people,dc=xxxx,dc=com" -s sub -D uid=zimbra,cn=admins,cn=zimbra -w zimbra
'(objectClass=zimbraAccount)' uid

real    0m0.004s
user    0m0.010s
sys     0m0.000s

With paged results:

zimbra@zre-ldap002:~$ time  ldapsearch -LLL -x -H
ldap://zre-ldap002.eng.vmware.com -b "ou=people,dc=xxxxx,dc=com" -s sub -D
uid=zimbra,cn=admins,cn=zimbra -w zimbra '(objectClass=zimbraAccount)' uid -E
pr=1000

real    0m1.204s
user    0m0.010s
sys     0m0.000s


Using paged results is fairly standard in Java clients, to prevent them from
hitting OOME's based on the way in which results are returned into a single
object.
Up to top level
Build   Contrib   Development   Documentation   Historical   Incoming   Software Bugs   Software Enhancements   Web  

Logged in as guest


The OpenLDAP Issue Tracking System uses a hacked version of JitterBug

______________
© Copyright 2013, OpenLDAP Foundation, info@OpenLDAP.org