#49501 Investigate transaction batching
Closed: wontfix 3 years ago by spichugi. Opened 6 years ago by firstyear.

Issue Description

In the code base we have support for transaction batching, which has been shown in some cases to improve our write performance. However, it is unknown if this option is stable, and @lkrispen suspects there was a locking problem.

Since this may yield a write performance benefit (which is often our weakness :( ) it would be good to investigate this option, as well as time limits on the batch commit (ie rather than entry threshold, but batch = 10 or 5 seconds elapse). We should investigate not only the batching stability, but also safe defaults and possible tunings.


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/2560

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata