-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
import pynwb is slow #1487
Comments
@mavaylon1 it would be helpful to run this through a profiler to see where the time is being spent. I assume the issue is likely that HDMF has to construct the TypeMap from the schema on import, but it will be good as a first step to get a clear understanding of where time is being spent so we can see what may be feasible to do to improve time for importing pynwb. |
Yes I think importing HDMF accounts for a good chunk of this. Thanks for looking into it. |
Running this through a profiler, hdmf accounts for roughly 46-50% of the time for importing pynwb. Within the time spent for hdmf, a very small portion is spent on backend, i.e objectmapper, builders, and manager. Using a more detailed profiler seems to point to loading the namespaces as a large factor in cumulative time spent. |
Related to #1050 and new issue #1255 . Initially, the problem with the linked approach of pickling the TypeMap is that it was not compatible with loading NWB extensions from a file. But I think this is not a completely blocking -- I think we can still pickle the TypeMap for the core namespace and load NWB extensions from a file. @mavaylon1 can you look into this? |
Importing
pynwb
is surprisingly slow on my machine. Is this typical for others?I think all my other packages are loading reasonably fast. For example,
h5py
loads in ~400 ms.The text was updated successfully, but these errors were encountered: