Skip to content
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

Unable to build stdlib on low memory computer #281

Closed
ghost opened this issue Dec 27, 2020 · 3 comments · Fixed by #282 or #283
Closed

Unable to build stdlib on low memory computer #281

ghost opened this issue Dec 27, 2020 · 3 comments · Fixed by #282 or #283

Comments

@ghost
Copy link

ghost commented Dec 27, 2020

When I attempt to build stdlib with make -f Makefile.manual, gfortran eats all available memory and it makes the computer unusable. Unfortunately there was no way to know if the process was about to end, then after 30 minutes I manually killed the gfortran process.

Here are the screenshots.

Command prompt
stdlib1

Task manager
stdlib2

Computer: Windows 10 x64, Memory (total): 8GB
gfortran: 10.2.0, x64

@LKedward
Copy link
Member

Hi @brocolis, please see this comment for a solution previously mentioned.

This is an issue/solution that should be mentioned prominently in the README.

Since you're already using fpm, you may want to try the stdlib-fpm package which limits the maximum rank because of this issue.


Is there a way to exploit submodules here and break templated routines across different compilation units? This could better exploit parallelism during builds and reduce peak memory usage.

@ghost
Copy link
Author

ghost commented Dec 28, 2020

Hi @LKedward . Both solutions work for me. Thank you.

@awvwgk awvwgk linked a pull request Dec 28, 2020 that will close this issue
@awvwgk
Copy link
Member

awvwgk commented Dec 28, 2020

Is there a way to exploit submodules here and break templated routines across different compilation units? This could better exploit parallelism during builds and reduce peak memory usage.

I tried to reduce the compilation load in #283 and got the default settings to compile with a peak memory usage of ~7 GB on two parallel build jobs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants