Closes #16. Use a single shared queue between all threads in each workload mapper.#19
Merged
Conversation
…ared queue between all threads in a single workload mapper.
Collaborator
|
One question, why is this IP based partitioning? To me, it looks like every command gets put into the same queue, and the threads pick up the commands regardless of IP. Am I missing something? |
xkrogen
changed the title
Collaborator
Author
|
Sorry, the commit message was a bit incorrect. I have updated the title & the description to more fully explain the issue we are solving here. |
Collaborator
|
LGTM, +1 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
On a single mapper in the workload replay, currently tasks are distributed to threads in a path-partitioned manner. This results in bad skew issues, where one thread can fall very far behind because it is overloaded. Thus, although all of the issues on a specific path get executed in order (though late), the ordering with other paths is very far out of sync. It is better to let some operations on the same path occur out of order so that (a) overall everything stays more in sync and (b) no thread falls far behind (which can delay the entire mapper from completing).