The connection code contains a special feature "turbo mode", which lets a worker thread continuously read a connection, without passing it back to the polling mechanism. This can enhance performance of very active connections. It is applied to replication connections by default, but if single replication operations like adding entries are relatively long, it could be better to apply them in parallel (the supplier already sends them asynchronously). Investigate if applying repl ops on a consumer in parallel, can be done without breaking replication (update of ruv?, urp?) and what the performance impact is. Probably making turbo mode configurable helps in investigation and to adopt to specific load scenarios
allow turbo mode to be disabled 0001-Ticket-565-turbo-mode-and-replication-allow-disable-.patch
commit 1c0c6b1 Author: Rich Megginson rmeggins@redhat.com Date: Wed Feb 13 07:18:27 2013 -0700
Metadata Update from @rmeggins: - Issue assigned to rmeggins - Issue set to the milestone: 1.3.1
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/565
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.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.