#47366 investigate performance of referential integrity plugin
Closed: wontfix 3 years ago by spichugi. Opened 10 years ago by lkrispen.

a customer, which was doing bulk MODRDN or DEL with one client connection noticed that at some point there was a gap of about 2 minutes in acceping a new operation.
It turned out that in these situations the referential integrity plugin was active in 5 threads and so the max threads per connection was exceeded, so the client had to wait until refinit postops were finished.
It should be investigated why it could take so long to complete refint. It looked the problem only started after a bulk of modrdns was already processed, so there could be a decline in performance over time


It was not that rapid to diagnose as the symptom (no new operation processed). A warning when a connection hit maxthread could be a help.

Metadata Update from @tbordaz:
- Issue set to the milestone: FUTURE

7 years ago

Maybe add more threads to RI plugin?

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None
- Issue close_status updated to: None
- Issue set to the milestone: 1.4.4 (was: FUTURE)

3 years ago

I don't know if more threads would help here, because we'll end up blocking around the DB to write, and lmdb/others are single thread write. More threads would allow us to identify integrity violations quicker, but that's assuming indexing etc.

I'd want to know more here but I wonder if the issue was a large group change or similar?

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

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