[389-users] high memory usage in 2.7.0

Hello, I am struggling to determine why 389-Directory/2.7.0 B2026.064.0000 is using a crippling amount of memory. I'm not married to 2.7.0, just looking for something stable and actively supported but not too new. We're running it in Docker on almalinux:9. If I set nsslapd-cache-autosize to much over 5 ns-slapd consumes memory and is killed by the OOM. I have increased docker's memory limit to that of the host but if it's smaller the same happens, sometimes just sooner as the OOM sees the process exceed Docker's limits. The server has 16gb of ram, I have turned off the NDN cache. ns-slapd is using 14gb of ram not leaving much for the OS. nsslapd-cache-autosize is set to 5, where is all of the memory going?? Here's the current state of the cache: # docker exec -it sdp389ds dsconf localhost monitor dbmon DB Monitor Report: 2026-07-02 17:24:32 -------------------------------------------------------- Database Cache: - Cache Hit Ratio: 89% - Free Space: 101.89 MB - Free Percentage: 51.3% - RO Page Drops: 14972351 - Pages In: 15086991 - Pages Out: 405261 Backends: - dc=philasd,dc=org (userRoot): - Entry Cache Hit Ratio: 13% - Entry Cache Count: 38259 - Entry Cache Free Space: 6.8 KB - Entry Cache Free Percentage: 0.0% - Entry Cache Average Size: 15.42 KB - DN Cache Hit Ratio: 97% - DN Cache Count: 336275 - DN Cache Free Space: 37.42 MB - DN Cache Free Percentage: 58.5% - DN Cache Average Size: 82.0 B # Any advice would be appreciated, I have to be missing something simple here! Thank you, -morgan -- _______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new