-
Notifications
You must be signed in to change notification settings - Fork 4
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
Extract to scalar OOM error #28
Comments
Thanks to @wangyuhan01 for raising saalfeldlab/paintera#293 initially. |
The process creates tons of HDF5 Sync threads. E.g. in one test case I observed as many as 5403(!!!!!!!!!) threads created by the HDF5 library. This is probably an issue with the underlying hdf5 library and how readers are created. Maybe each reader creates a sync thread. @igorpisarev have you ever observed anything like this in any of your spark jobs when converting to hdf5? |
That indeed looks very strange. I haven't really used hdf5 for conversion except for only a couple of experiments, but I don't recall seeing this, or at least it wasn't a problem. Does the converter here write into HDF5? I though that it always writes out N5, but can take HDF as an input. |
@igorpisarev This does not affect the One of the use cases is extraction into an h5 container for easier processing in some scenarios, e.g. Python. I will try with the |
When running
extract-to-scalar
to save into an HDF file, this error may occur (have not reproduced yet):It looks very suspicious that a lot of threads would be created.
The text was updated successfully, but these errors were encountered: