-
Notifications
You must be signed in to change notification settings - Fork 21
Load time #155
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
Comments
I agree completely. We indirectly employ Py-ART lazy dictionary loading, but maybe we could do this more extensively with the internal code. We should also expand the testing.... |
in my system with empty cache it takes 17s to load pyart and just around 1.5s to the rest of artview. So we can not do much. from those 17s, around 7s are just to load basemap. What about a lazy loading there @jjhelmus? |
@gamaanderson Can you be more specific in what you mean by "loading". Are you looking at the time it takes to |
I mean import, it does take so much, but for that I must empty the RAM cache. subsequent runs are faster. |
I did some profiling the other night. The pyart import remains somewhat slow, but I also noted that PyQt was loading very slowly it seemed. I don't have extensive evidence yet, but this is something to keep in mind and test in the future. |
as any graphical program artview takes some time to load, but it is kind to annoying me. We should check if there is no unnecessary loading or if there are things we can load just when we need it.
We could add some profiling to generate statistics of which functions are taking to much time. As we work on python it is important to optimise it once in while.
The text was updated successfully, but these errors were encountered: