You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I use omx-java to write out a lot of omx files. But at some point save() in OmxFile.java slows down extremely, finishing maybe 24-48 hours later. Next file begins writing - same thing again. The slow-down happens after approx. 2700 files (each omx file contains 1 double matrix à 10-70 MB having roughly 5500x5500 entries). It does not happen at a specific file. Meaning the same file for which writing slowed down will be generated without any problem after a restart of the code.
I think the issue is within the HDF5 library, since the slow-down happens in hdf5File.save().
Do you maybe know this problem and do you have a solution for this?
I read that some HDF5 config parameters could be changed, but unfortunately I have no clue what the real problem is or how to even change these HDF5 config parameters in java. My solution so far is to automatically catch the "stuck" situation (using a thread for save() and thereby excluding a java garbage collector problem, since nothing else slows down) and restart the code.
Thanks in advance!
The text was updated successfully, but these errors were encountered:
Hi,
I use omx-java to write out a lot of omx files. But at some point save() in OmxFile.java slows down extremely, finishing maybe 24-48 hours later. Next file begins writing - same thing again. The slow-down happens after approx. 2700 files (each omx file contains 1 double matrix à 10-70 MB having roughly 5500x5500 entries). It does not happen at a specific file. Meaning the same file for which writing slowed down will be generated without any problem after a restart of the code.
I think the issue is within the HDF5 library, since the slow-down happens in hdf5File.save().
Do you maybe know this problem and do you have a solution for this?
I read that some HDF5 config parameters could be changed, but unfortunately I have no clue what the real problem is or how to even change these HDF5 config parameters in java. My solution so far is to automatically catch the "stuck" situation (using a thread for save() and thereby excluding a java garbage collector problem, since nothing else slows down) and restart the code.
Thanks in advance!
The text was updated successfully, but these errors were encountered: