-
Notifications
You must be signed in to change notification settings - Fork 235
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
How much memory is needed to compile? #311
Comments
Hi, |
We should changed the docs should to -j 4.
|
I think this is oddly specific to AWS machines. I noticed |
Without the number, make will run in parallel without limit which is always
a bad idea. Best not encourage people to do that
…On Sat, Jan 18, 2020, 11:05 PM Marcin Junczys-Dowmunt < ***@***.***> wrote:
I think this is oddly specific to AWS machines. I noticed make gets the
number of CPUs/threads wrong there (because they are VMs?) and dispatches a
much larger amount of processes than available threads.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#311?email_source=notifications&email_token=AAFI4FEHU4FL4Q4QQ5P6AY3Q6P3VBA5CNFSM4KIXQAUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJKKV5Y#issuecomment-575974135>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFI4FHSF4HAGE3NN62IZ63Q6P3VBANCNFSM4KIXQAUA>
.
|
At least a comment about the potential memory issue is a good idea. Usually people compile on larger machines if they have GPUs, though. |
Thank you for the very quick responses! |
I'm getting a
virtual memory exhausted: Cannot allocate memory
error when I try to compile (on the
make -j
step).I'm running this on an AWS EC2
g4dn.xlarge
machine which has 16GB RAM. Do I need more than that just to compile? When I run the make I indeed seefree
show memory usage steadily going up until the error appears and the build crashes.The text was updated successfully, but these errors were encountered: