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

Memory allocation problem when running 127 jobs on joplin #32

Open
sandrinebedard opened this issue Feb 2, 2021 · 3 comments
Open

Memory allocation problem when running 127 jobs on joplin #32

sandrinebedard opened this issue Feb 2, 2021 · 3 comments

Comments

@sandrinebedard
Copy link
Member

When running 127 jobs in parallel on joplin for preprocessing, this error occurs in gradunwarp for some subjects:

MemoryError: Unable to allocate 208. KiB for an array with shape (208, 256) and data type float32

gradunwarp uses a lot of memory as discussed here

Solution:
I trided reducing the number of jobs running in parallel with sct_run_batch -> with the flag -jobs 120, everything went smoothly. I would conitnue this way for future preprocessing of the rest of the Uk biobank dataset. Not sure how to add this to the README; maybe put a warning or something like that because this solution is for this case specifically.

@jcohenadad
Copy link
Member

Right, I also ran into some problem when maxing out the available cores. For the spine-generic pipeline, i used maximum 20 cores (!) to avoid running into problems with the sct_deepseg_sc function, which maxes out the RAM.

@sandrinebedard
Copy link
Member Author

Ok thanks for the info! I will remember that for when I generate the segmentations! On Compute Canada, we are creating batches of 32, should we be worried that the RAM will be maxed out also? (I will discover it quickly either way)

@jcohenadad
Copy link
Member

32 on compute canada should be fine (i ran aggressive pipelines with that number of cores, so it should be OK)

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

No branches or pull requests

2 participants