That will heavily depends on the hardware used, cpu arch, i/o for disk.
An "old" hardware can get a few hundred entries per sec.
You should be able to get several thousand entries per second with
"recent" hw, should reasonably be under 15 minutes.
A small virtual machine can get 500 entries per s
Hi All,
I am fairly new to LDAP administration and was wondering approximately how
long it should take to import approximately 500,000 user records.
I have tried from both the administration console as well as the from the
command line and everything seems to be taking forever (days). I don't ha
6 minutes for 25000 entries is obviously too much. On our server (HP of two
years old ang 2Go of memory) 8300 entries are returned in 0.77 seconds (the
filter is almost like yours - "(&(uid=*)(objectClass=inetOrgPerson))").
There is certainly some problem either with the disk access or with the
m
> How many entries match this search filter? Is your nsslapd-idlistscanlimit
> high enough to hold both all of the uid=* entries and all of the
> objectClass=sambasamaccount entries?
We have about 25000 sambaSamAccount objects. nsslapd-idlistscanlimit
is set to 5 (total object are about 4
Juan Asensio Sánchez wrote:
Hi, thanks for your answer.
2009/10/27 Andrey Ivanov :
Hi,
Do you make the ldapsearch on the same server where ldap server turns?
Yes, sure.
I think your server does not freeze. When you receive the result search
entries the CPU of your server is occ
One core at 100% is to be expected if you're executing a long-running
(unindexed) search
over data that's mostly already in memory.
What's not expected is that other concurrent operations (even on the
same connection)
should block. Generally that shouldn't happen. You might try turning up
the l
Hi, thanks for your answer.
2009/10/27 Andrey Ivanov :
> Hi,
>
> Do you make the ldapsearch on the same server where ldap server turns?
Yes, sure.
> I think your server does not freeze. When you receive the result search
> entries the CPU of your server is occupied at 100%.
Yes, if I monitor t
Hi,
Do you make the ldapsearch on the same server where ldap server turns?
I think your server does not freeze. When you receive the result search
entries the CPU of your server is occupied at 100%. If it is a virtual
machine that you are using try to add another cpu. Instead of showing the
resul
Hi
I have made these changes to the directory:
dn: cn=config
- nsslapd-sizelimit: 5
- nsslapd-timelimit: 60
- nsslapd-maxdescriptors: 65535
dn: cn=config, cn=ldbm database, cn=plugins, cn=config
- nsslapd-idlistscanlimit: 5
- nsLookThroughLimit: 5
- nsslapd-dbcachesize: 838860800 (=8
