On 11/25/2015 12:35 AM, Petteri Jekunen wrote:
Hi,
Is it just ordinary behavior with 389 DS that search results may take
a very loong time just after starting the server when there are no
entries in the cache yet?
Yes.
And when the cache is fully saturated (enough cache configured for all
the entries) results become dramatically down - for instance from 4
minutes to 4 seconds.
Yes.
If this this is so, is there anything that could be done to fill in
the cache automatically after startup?
Yes. Do
ldapsearch -D "cn=directory manager" -w "password" -b
"dc=your,dc=base,dc=suffix"
'(|(objectclass=*)(objectclass=ldapsubentry)(objectclass=nstombstone))'
> /dev/null
just after the server starts. This will probably take several minutes
or more, but after that, every single entry in the database will be
cached (assuming you have enough RAM - use dbmon.sh to check).
We have some 60 000 entries, RHEL 7.1, 389-Directory/1.3.3.1
B2015.267.1737 on VMWare.
We have quite a heavy use of roles, and this seems to be a significant
issue especially with them - or at least with them.
We have used the Sun DSEE previously and are quite new to 389 DS. The
technology seems very similar although.
Thanks a lot in advance!
Regards,
Petteri Jekunen,
Tampere University of Applied Sciences
--
389 users mailing list
389-users@%(host_name)s
http://lists.fedoraproject.org/admin/lists/389-users@xxxxxxxxxxxxxxxxxxxxxxx
--
389 users mailing list
389-users@%(host_name)s
http://lists.fedoraproject.org/admin/lists/389-users@xxxxxxxxxxxxxxxxxxxxxxx
