Improve version pipelining on the proxy #2589
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The resolvers and tLogs must process commits in the same order the master gives out versions. Therefore if a proxy gets a version from the master while it already has a ton of other batches it needs to submit to the transaction logs, it will create a situation where the resolvers and tLogs have to wait a long time for that version to be submitted before it can process requests from other proxies.
A proxy always works on the commit the is closest to completion, so there is no reason to get a version if we know the proxy already has a lot of CPU work it must do for other batches that are already in process.