Disk I/O can be the most common bottleneck, make sure you have enough physical memory to fit id2entry may be one. There are also a few recommendations at http://docs.redhat.com/docs/en-US/Red_Hat_Directory_Server/9.0/html/Performa... You can move the BDB transaction logs (*.log) in a separate filesystem, tune db cache, add indexes. And more: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Performanc... M.

On 02/01/2012 03:08 PM, Mark Reynolds wrote:

Hi Marco,

This is isn't linux specific, but disabling the logs(access & error) can help. If you need the logs, move them to a dedicated FS. I don't know if Linux has a FS cache, but on Solaris I've seen it is sometimes more efficient to turn the DS cache settings all the way down, and allow the OS FS cache to do everything.

Best Regards, Mark

On 02/01/2012 04:03 PM, Marco Pizzoli wrote:

...

Hi *, I'm exploring 389 after few years with OpenLDAP and I'm curious to know if some perfomance tuning tricks on Linux are valid with this product too.

• having a db directory located in a dedicated filesystem mounted

with the "noatime" option

• LD_PRELOAD=tcmalloc

Any other hints?

Thanks in advance Marco

-- _________________________________________ Non è forte chi non cade, ma chi cadendo ha la forza di rialzarsi. Jim Morrison

-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users

-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users