This is just a potential RFE. Please, feel free to close it if you consider it irrelevant.
Many large deployments are having performance problems which are solved once caches configured and the db loaded in cache.
But for that a first ldapsearch is done to be able to load the whole db in cache or all what is possible.
I was wondering whether it could not be a parameter at backend level to indicate "prime cache" as possible at startup.
Per ticket triage, setting FUTURE for now.
Metadata Update from @nhosoi: - Issue set to the milestone: FUTURE
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to None - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1286
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.