Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tune-up chunking #47

Merged
merged 14 commits into from
Sep 12, 2024
Merged

Tune-up chunking #47

merged 14 commits into from
Sep 12, 2024

Conversation

akhanf
Copy link
Member

@akhanf akhanf commented Sep 2, 2024

This PR makes changes to the default chunking, to fix issues happening with bigstitcher and fusion where too many threads and too large chunks were causing memory and garbage collection issues that were stalling the run..

Problem is likely because we had large-ish 2d chunks, but the processing was requiring 3d context, so ultimately too much memory was being allocated when tryibng to load the 3d data..

This also makes some fixes/updates to the tif stack to zarr

akhanf and others added 14 commits September 2, 2024 15:56
also set dtype to int16 (in case it is related to the black bars bug)
using the fsstore was giving us all zeroed niftis. not sure why
To hopefully address performance issues in the bigstitcher step when
dealing with large datasets.

Also sets dtype to int16 instead of uint16 for this only -- some imagesc
posts describing the black bars had this as a fix..
and moves rechunking from zarr2bdv to apply_flatfield_corr
should hopefully improve performance
since that likely wasn't correcting the problem
@akhanf akhanf changed the title Tune garbage collection params Tune-up chunking Sep 12, 2024
@akhanf akhanf merged commit e32ec07 into main Sep 12, 2024
4 checks passed
@akhanf akhanf deleted the tunegc branch September 12, 2024 22:23
akhanf added a commit that referenced this pull request Sep 14, 2024
Needs to be 128x128x128 or 256x256x256 instead of 1x4096x4096. The latter causes memory issues as described in #47
akhanf added a commit that referenced this pull request Sep 14, 2024
* chunk size (pre bigstitcher) wasn't set correctly

Needs to be 128x128x128 or 256x256x256 instead of 1x4096x4096. The latter causes memory issues as described in #47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant