Hi all,
I've attached an RFC document describing some new API functions that improve how hyperslab selections can be created and operated on in HDF5. Please take a look and let me know what you think.
Also, as a teaser, the changes to implement these in the HDF5 library are showing nice performance improvements for some popular application usage patterns, so they should be good for more than just the new functionality.
Hi all,
I've attached an RFC document describing some new API functions that improve how hyperslab selections can be created and operated on in HDF5. Please take a look and let me know what you think.
Also, as a teaser, the changes to implement these in the HDF5 library are showing nice performance improvements for some popular application usage patterns, so they should be good for more than just the new functionality.
Hi all,
I've attached an RFC document describing some new API functions that
improve how hyperslab selections can be created and operated on in HDF5.
聽聽Please take a look and let me know what you think.
API looks fine. I cannot draw to mind a case where I would need such functionality, or where the "dataset copy + hyperslab selection" bit was a significant -- or detectable -- portion of runtime overhead, but there are lots more HDF5 workloads out there than *I* regularly encounter.
some kind of funny extra formatting on top of page 4:
a)
b)
3 Interface
Also, as a teaser, the changes to implement these in the HDF5 library
are showing nice performance improvements for some popular application
usage patterns, so they should be good for more than just the new
functionality.
you are saying that in order to make hyperslab selection more flexible for these special cases, you've improved performance for the common cases? sorcery!
==rob
路路路
On 06/13/2014 10:02 PM, Quincey Koziol wrote:
--
Rob Latham
Mathematics and Computer Science Division
Argonne National Lab, IL USA
