Hmm. That *does* sound really bad. I don't have a lot of experience with attributes but am wondering about H5Aiterate.
Would using that approach to accessing your attribute data improve performance? Reason I think it could possibly is that it wouldn't be constantly be having to map an attribute name and if you are opening most of the attributes on a given object, iterating them might go faster. But, that is only a guess. Mark "Hdf-forum on behalf of Deepak 8 Kumar" wrote: Hello! I have a HDF5 based application to read the hdf5 file which has almost 3200 groups and 56000 attributes. The application is using the standard hdf5 api and it took almost 11 minutes to read only the groups and attributes. I used StopWatch and observed that H5Aopen_name() is taking almost 97 percent of the total time. I am using HDF 1.10.1 Windows10 x64. My question is that is this the expected behavior here with H5Aopen_name() or I am not reading it properly? What approach we should take in this kind of file with large number of attributes? Any insight is greatly appreciated. Thanks, Deepak Kumar
_______________________________________________ Hdf-forum is for HDF software users discussion. [email protected] http://lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org Twitter: https://twitter.com/hdf5
