WIP Experimental integration of nocopy cloudpickle with bytelist API #1643
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.
This is a work in progress integration of an experimental branch of cloudpickle that allows for nocopy dump and load of nested numpy arrays using a bytelist API.
This relies on: cloudpipe/cloudpickle#138
In particular, this should help make the workers more stable when dealing with large numpy arrays or pandas data frames: spilling to disk (and loading back spilled data structures) should no longer incur large temporary buffer allocations. Also the
_BytelistFilehelper class is not properly tested.There are broken tests (e.g. I just noticed that pickling arrays of objects is broken) but I wanted to do a full run on CI and communicate about the final goal of my work on cloudpickle to other cloudpickle and dask developers.