Allow spawning serialization to threads for large objects #2944
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
wjsi
force-pushed
the
enh/ser_thresh
branch
2 times, most recently
from
01360d0 to
0a07b42
Compare
qinxuye
pushed a commit
to qinxuye/mars
that referenced
this pull request
Apr 21, 2022
qinxuye
pushed a commit
to qinxuye/mars
that referenced
this pull request
Apr 21, 2022
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.
What do these changes do?
Allow spawning serialization to threads for large objects. When the number of objects is larger than certain threshold, serializing will be moved into a ThreadPoolExecutor.
Related issue number
Fixes #2942
Check code requirements