Hi,
I have made changes such that backend BDB ( ver 4.5 ) resides in memory instead of on disk . This is with default slapd configuration. I was hoping to have a better performance with this. But what I now see is that do_add takes much more time then what it use to take when BDB was on-Disk. Indexing is done on objectclass in both the cases.
Any pointers on why this could be an issue?
Regards, Suhel
Suhel Momin wrote:
Hi,
I have made changes such that backend BDB ( ver 4.5 ) resides in
memory instead of on disk . This is with default slapd configuration. I was hoping to have a better performance with this.
back-bdb as currently residing in HEAD already yields efficiencies of 95% of available system bandwidth. It is extremely unlikely that you are going to be able to improve the performance significantly, most changes you could make to the code at this point will only yield performance losses.
But what I now see is that do_add takes much more time then what it use to take when BDB was on-Disk. Indexing is done on objectclass in both the cases.
Any pointers on why this could be an issue?
<quote who="Suhel Momin">
Hi,
I have made changes such that backend BDB ( ver 4.5 ) resides in
memory instead of on disk . This is with default slapd configuration. I was hoping to have a better performance with this. But what I now see is that do_add takes much more time then what it use to take when BDB was on-Disk. Indexing is done on objectclass in both the cases.
Any pointers on why this could be an issue?
This should be a openldap-software e-mail.
What are your changes?
DB_CONFIG settings?
Gavin.