-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Command killed due to excessive memory consumption #6025
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'd like to take a look at this. Probably next week if I have some time. I think conda gets crazy when using multiple channels :/ My first attempt was to upgrade the @fmaussion where I can see what packages will be installed by |
Thanks for your help @humitos ! your question motivated me to try to install the packages directly instead of via Change in env: https://github.com/OGGM/oggm/pull/835/files Build log: https://readthedocs.org/projects/oggm/builds/9457124/ Thanks for your help and sorry for the noise... |
@fmaussion awesome! thanks for sharing the results! |
@humitos if you agree I'd like to reopen this. In a sister project (with exactly the same env.yml) we are experiencing the memory issue at the conda step: https://readthedocs.org/projects/rgitools/builds/9481900/ Any idea on how to make it more efficient? |
@fmaussion I've already add the flag to update conda on startup but it still fails. Is it possible to remove all the dependencies that are not needed to build the documentation from the environment.yaml? For example, with a quick look, it seems that |
Also, you may want to consider to no use conda |
@humitos (and @ocefpaf and @jswhit because I think they might be interested in this). I just managed to do something that would have been impossible a year ago: I moved to a full Here the requirements: https://github.com/OGGM/rgitools/blob/master/docs/requirements.txt And the setup:
The pinning of netCDF4 to a 2017 version were necessary for the netcdf4 library to work without an obscure After moving from pip to conda, then mamba, are we going back to pip again? 😉 Thanks to wheels, on linux this is at least an option. |
@fmaussion I'm happy that you find out a way to make it builds the docs on Read the Docs without conda. I would love if you can keep me posted (or I can subscribe to an issue in your repo) since I'm interested on tracking this kind of issues on Read the Docs and collect some ideas, workflow problems, etc to continue thinking in different solutions. |
Dear Maintainers, dear @humitos - our builds started to fail because of timeout errors again, without any significant change on our side: https://readthedocs.org/projects/oggm/builds/10371200/ I you have time I'd be grateful about any advice about what's going on. Thanks!!!! |
OK, nevermind - I think the problem is on our side, sorry for the noise. |
Details
Hi! I'm here again, with our expensive conda builds (for the context, I already had performance related issues in the past: #5098 , #4432).
Our projects simply requires a lot of packages, and conda has become very hungry lately. Can I ask for a higher memory limit for the following projects? They all have the same package requirements:
Note that we would really love to be more efficient than that, but I really don't think we can. We also have working containers that could create our docs for you, but ReadTheDocs still doesn't accept arbitrary containers, right?
Thanks in advance!
Fabien
Expected Result
The docs being built.
Actual Result
Command killed due to excessive memory consumption
The text was updated successfully, but these errors were encountered: