BDB has several different levels of transaction isolation. We may be able to gain some write performance by using a different level. See
http://docs.oracle.com/cd/E17076_02/html/gsg_txn/C/txnconcurrency.html
http://docs.oracle.com/cd/E17076_02/html/gsg_txn/C/isolation.html
http://docs.oracle.com/cd/E17076_02/html/programmer_reference/transapp.html
http://docs.oracle.com/cd/E17076_02/html/programmer_reference/transapp_read.html
achieve this with mdb? Could also achieve this with bdb using MVCC - but there is the entry/dn cache per transaction problem
achieve this with mdb?
Could also achieve this with bdb using MVCC - but there is the entry/dn cache per transaction problem
Metadata Update from @nhosoi: - Issue assigned to nhosoi - Issue set to the milestone: 1.4 backlog
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/439
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.