Repository navigation
Node 12 dynamic heap size maxes out at 2048MB #28202
Description
Activity
Is #25576 (comment) informative?
Reacted by Jan Lohage, Michael Loughry, Filipe Silva, Bruno Schäpper and Kevin McBrideIt's informative as to how it's currently implemented, but I'm not sure I gleaned enough (nor know enough) about V8 to understand why.
Is there a reason the ceiling can't be raised further? Or even dynamically changed at runtime with something like
v8.setFlagsFromString()?The current default comes from V8 so it would be more effective to ask in places like https://groups.google.com/forum/#!forum/v8-users
@sam-github it is very informative, thank you. This definitely is intentional. The comment also mentions that the maximum is likely too low and should be reviewed:
With this spelled out, it is worth pausing and thinking about this more deeply. I do think we need change the default on large machines. I routinely see workloads where the job fails with 'out of memory' when there clearly is enough memory available.
@joyeecheung #25576 (comment) is altering the limit to not be the default v8 one though. So I feel this is actually the right project to discuss the current limit.
Hi there. The Node 12 announcement contained a section about dynamic heap limits:
The "will configure the JavaScript heap size based on available memory" part made me think the new limit was always relative to the total available memory. But as far as we can tell in angular/angular-cli#13734 (comment), there's still a default maximum at 2048MB.
Is this new default maximum intended? The blog post doesn't mention any maximum, just that it's based on available memory.