Release slab memory to the OS between iterations#202
Open
chourroutm wants to merge 1 commit into
Open
Conversation
Copying/downsampling processed slabs with steadily growing resident memory: the large numpy copy buffers and tensorstore shard-encode buffers were freed at the Python level but retained in the glibc allocator arena rather than returned to the OS, so RSS ratcheted up slab-by-slab until a memory-capped session was exhausted. - Add _release_memory() (gc.collect + guarded glibc malloc_trim) and call it at the end of _copy_slab and _downsample_block after dropping the slab/shard buffers and tensorstore handles. - Bound the tensorstore cache pool so the downsample read path cannot grow an unbounded in-memory cache. - Build the joblib job list lazily so each slab's dask view is released as it completes instead of all being pinned for the whole call. - Document that peak memory scales with n_processes.
This file contains hidden or 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
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.
Copying/downsampling processed slabs with steadily growing resident memory: the large numpy copy buffers and tensorstore shard-encode buffers were freed at the Python level but retained in the glibc allocator arena rather than returned to the OS, so RSS ratcheted up slab-by-slab until a memory-capped session was exhausted.