Skip to content

Conversation

@svensht2
Copy link

//cc @limorhe @giadang

this is the direction I'm thinking for loading our datasets

@giadang
Copy link

giadang commented Jul 20, 2018

I'm fine with this except the open/close the h5 files every time you call the function _read_hdf5_func, which may cause the overhead as people are talking about. Is there a way you can pre-open those h5 files and store them into something like a dictionary, and inside the function _read_hdf5_func you only need to get the right h5 object instead of opening/closing it again and again?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants