On Mon, 2017-06-05 at 20:30 +0000, Paul Whitney wrote: > LOL, that is ironic. Well we also discovered a significant boost by > increasing the normalize DN cache limits from 20MB to 1GB. While 1GB > may be overkill, without any real metric to compare against, we have > the RAM to use and figure lets just give it a large cache. Our > metrics improved dramatically again. Our average look ups are now > mostly in the sub-second times. DN and NDN cache are not yet being tuned as part of the auto-tuning, but there is an open issue for me to improve this situation. [0] As well, the NDN cache never made things "as fast" as we hoped, but I've looked at the code and there is plenty of room to improve. I'll open an issue about this too. [1] Hope that helps, [0] https://pagure.io/389-ds-base/issue/48831 [1] https://pagure.io/389-ds-base/issue/49280 -- Sincerely, William Brown Software Engineer Red Hat, Australia/Brisbane
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
