This repository has been archived by the owner on Jan 3, 2024. It is now read-only.
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.
It turns out if you increase the size of a dask array using
da.repeat(...)
, dask is clever and doesn't make actual copies of the data. This is great, unless you're running memory benchmarks and want the memory useage to increase 🙈This PR changes the sample data to be random data generated by dask, instead of repeating existing data. Although the cell detection results won't be meaningful on this data, it provides a easy way to run memory benchmarks.
To confirm this works, here's the memory usage of just detection, which shows a clear increase when the array size is increased:
Repeats = 1
Repeats = 2