-
Notifications
You must be signed in to change notification settings - Fork 10
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
rex is >7x slower than hsds #169
Comments
Not sure off the top of my head... On first glance yes this is surprising. The rex resource classes should not be doing anything too fancy here. Some ideas (none of which i am fully convinced by):
Ideas for a more direct comparison:
|
Thanks for the suggestions Grant. Looking at
The use of |
The "extraction" classes add some quality-of-life features (e.g., lat/lon lookup and SAM dataframe extraction) but are ultimately just wrappers of the base resource classes (e.g., WindResource). We typically advertise the extraction classes to the public because of the nice features but the base resource classes have less overhead. |
Grant, Using A formal code profile is outside the scope of my time to solve/ help with this issue. I was not exactly sure what you meant with suggestion 4 above so I did not try it but I would not expect it to make much of a difference.
|
okay well thanks for the heads up about the possible performance issues! |
I wrote the script at the bottom of this issue to spot check the performance of using hsds vs rex when I noticed rex taking significantly longer to run than hsds for the same call.
This issue is really just a question to if you guys have an idea as to why this is or if this is to be expected for some reason?
Comparison of Execution Times (in seconds):
On average, the HSDS method is faster by a factor of 7.62.
HSDS Method:
Rex Method:
The text was updated successfully, but these errors were encountered: