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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EH Pyproto] Async recv perf improvement #23122
[EH Pyproto] Async recv perf improvement #23122
Changes from 6 commits
d9d2150
153592d
9a8031d
77e8820
a054f4f
32d1cd4
5e264f7
820d650
0374f0b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does the lock around this achieve?
We're no longer processing the incoming message batch concurrently with
gather
- so shouldn't that remove the possibility of a race condition?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we have two coroutines interacting with self._message_buffer simultaneously -- receive task keeps adding messages while callback task keeps pumping messages, race condition between the two tasks is what I'm trying to avoid here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could investigate this further in term of optimization - it seem expensive to await the lock for every individual message.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah.. it is interesting that actually in my v0, I indeed tried to batch things, however, I guess I didn't do thing correctly that the perf is not good.
I can put a todo for this