-
Notifications
You must be signed in to change notification settings - Fork 104
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
Performance loss with new base image? #842
Comments
Note that this is maybe not super important - py37 seems largely unaffected. |
asv uses conda using one of the generated environment files: I'm not sure why the new container would be so much slower though. It contains a lot of updates, last time we had random slowdown it was an issue with newer netCDF4 versions. |
For the record, here is the output of pip3 list --format=freeze for the two base images. 20190613
20190802
The diff between them
|
Interesting how the June Image has matplotlib 3.1.0, but was running our tests just fine for months. |
xarray and numpy are good candidates for performance changes. But in order to know this we would need more systematic tests, e.g. with asv (our benchmarks are not yet complete enough to ensure a good performance coverage, though... should work on this...) |
numpy was the first thing I just tested, and it does not appear to change anything to downgrade it back to the old version: https://travis-ci.org/TimoRoth/oggm/builds/567823025 Edit: looking at it some more, it does seem to have some impact, but it's not back to the old numbers. |
This is now definitely attributed to numpy: numpy/numpy#14281 Closed in favor of #855 |
For #814, I switched to a new base image.
The performance loss is clearly visible, and for some tests so important that the tests now time out. See the time differences between these two:
@TimoRoth do you have an idea how to test this?
Related question: what environment do we use on asv? https://cluster.klima.uni-bremen.de/~github/asv/#/ - if we don't use our docker images yet, we might consider using them if possible.
The text was updated successfully, but these errors were encountered: