Share delayService across clients #35
Open
Conversation
This file contains 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
delayService normally feeds into the eventLoop which has a max of 2 * num core threads shared across all clients created in the drift session. We should not need more than the number of threads that are being used by the eventLoop
arhimondr
approved these changes
Apr 21, 2021
wanglinsong
force-pushed
the
master
branch
5 times, most recently
from
f6789f1 to
ffd0e7f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
delayService normally feeds into the eventLoop which has a max of
2 * num core threads shared across all clients created in the drift
session. We should not need more than the number of threads that
are being used by the eventLoop