-
Notifications
You must be signed in to change notification settings - Fork 13
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
[BUG/ISSUE] Large memory requirement at compile time prevents automated build #4
Comments
Nothing comes to mind for why the memory requirement is so large. Have you tried to isolate if it is from compilation of ESMF or MAPL specifically? If it is MAPL, this is something we could potentially bring up with GMAO. |
Looks like it crashes even when compiling ESMF (haven't got to MAPL yet):
|
We want to eventually use a pre-built ESMF which would solve this problem if the large RAM requirement is only from building ESMF. You can isolate the RAM needed to build everything except ESMF by compiling ESMF successfully so that you have file esmf.install) and then doing make compile_mapl. |
Ha, it turns out that Full log files, tested on EC2 t2.micro, t2.small, t2.large:
So this problem should be solved by using pre-built ESMF. |
Great. I will close this issue since we have a path forward, although it might take some time. |
I am able to build GCHP Docker image on a large EC2 instance (>10 GB RAM), but fail to do so with automated build on Docker Hub because of the 2 GB RAM restrictions on Docker Hub
Here's the full build log:
https://hub.docker.com/r/zhuangjw/gchp_model/builds/b4bvaupogcmwvy5dcc9nzdw/
Any idea why GCHP needs so large memory at compile time?
The workaround is to build Docker images locally (e.g. on AWS) and uploaded to Docker Hub.
Alternatively I can try building Docker images on TravisCI. Travis has 7.5 GB RAM and should probably work.
The text was updated successfully, but these errors were encountered: