4 ms·
I use HDF5 extensively, why is it horrible? It seems for a different use case, column-oriented numerical data vs. "database" record-type data.
by radarsat1 8y ago
I use HDF5 extensively, why is it horrible? It seems for a different use case, column-oriented numerical data vs. "database" record-type data.
- Const-me 8y agoToo slow. It's 2018, modern PCs have 8 cores and 16 hardware threads, HDF5 only uses 1 at a time: https://support.hdfgroup.org/HDF5/faq/threadsafe.html https://support.hdfgroup.org/HDF5/faq/threadsafe.html And that's C API, C++ will just crash instead. The case is different threads processing different files, not concurrent access to the same file (the latter would be very nice but I understand why it's quite hard to support). Also looks like C++ API was designed in 90-s. Maybe that's my personal preference but I find it hard to work with, too much OOP but too few types.