You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's been brought up on the mailing list (citation needed) that some people want to run Go with heaps beyond the default limit (128 GB today).
Perhaps we should revise the limit at each Go release according to some metric. One possible metric would be to make sure that Go can address all the memory available on the largest VM you can rent from Amazon or from Google.
The text was updated successfully, but these errors were encountered:
I think adjusting MaxMem automatically on ulimit -v setting is more useful,
and it will also help the problem in the other direction (Go processes use
so much VM that os/exec fails: see
#5838 (comment))
It's been brought up on the mailing list (citation needed) that some people want to run Go with heaps beyond the default limit (128 GB today).
Perhaps we should revise the limit at each Go release according to some metric. One possible metric would be to make sure that Go can address all the memory available on the largest VM you can rent from Amazon or from Google.
The text was updated successfully, but these errors were encountered: