Get rid of copy memory when receive and send message #34
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
rafa-be
previously approved these changes
Oct 14, 2024
sharpener6
force-pushed
the
main
branch
2 times, most recently
from
f3b954c to
dcaab78
Compare
rafa-be
previously approved these changes
Oct 16, 2024
Signed-off-by: Sharpner6 <[email protected]>
Signed-off-by: Sharpner6 <[email protected]>
Signed-off-by: Sharpner6 <[email protected]>
rafa-be
approved these changes
Oct 16, 2024
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.
Hopefully this will use zero copy, but it's rely on pyZMQ's implementation, if this still doesn't solve copy problem (should use zero copy), we will need implement c/c++ version of client agent + scheduler + worker agent.