blocks|key|725545|text|“旧空间”是V8托管(也就是垃圾收集的)堆(即JavaScript对象所在的地方)中最大和最可配置的部分，而--max-old-space-size标志控制它的最大大小。随着内存消耗接近极限，V8将花费更多的时间在垃圾收集上，以便释放未使用的内存。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|725546|如果堆内存消耗(即GC不能释放的活动对象)超过限制，V8将使您的进程崩溃(因为没有其他选择)，因此您不希望设置得太低。当然，如果设置得太高，那么V8允许的额外堆使用可能会导致整个系统耗尽内存(或者交换或终止随机进程，因为没有其他选择)。|725547|总之，在一台内存为2GB的机器上，我可能会将--max-old-space-size设置为1.5GB左右，以便留下一些内存用于其他用途，并避免交换。|725548|entityMap^0|1I|K|0|0|M|K|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|K|$]]

"Old space" is the biggest and most configurable section of V8's managed (aka garbage-collected) heap (i.e. where the JavaScript objects live), and the <code>--max-old-space-size</code> flag controls its maximum size. As memory consumption approaches the limit, V8 will spend more time on garbage collection in an effort to free unused memory.

If heap memory consumption (i.e. live objects that the GC cannot free) exceeds the limit, V8 will crash your process (for lack of alternative), so you don't want to set it too low. Of course, if you set it too high, then the additional heap usage that V8 will allow might cause your overall system to run out of memory (and either swap or kill random processes, for lack of alternative).

In summary, on a machine with 2GB of memory I would probably set <code>--max-old-space-size</code> to about 1.5GB to leave some memory for other uses and avoid swapping.

blocks|key|1448576|text|当分配给正在执行的应用程序的内存少于所需内存时，就会发生此错误。默认情况下，Node.js中的内存限制为512+MB。要增加这个数量，您需要设置内存限制参数—-max-old-space-size。它将有助于避免内存限制问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1448577|node+--max-old-space-size=1024+index.js+#increase+to+1gb
node+--max-old-space-size=2048+index.js+#increase+to+2gb
node+--max-old-space-size=3072+index.js+#increase+to+3gb
node+--max-old-space-size=4096+index.js+#increase+to+4gb
node+--max-old-space-size=5120+index.js+#increase+to+5gb
node+--max-old-space-size=6144+index.js+#increase+to+6gb
node+--max-old-space-size=7168+index.js+#increase+to+7gb
node+--max-old-space-size=8192+index.js+#increase+to+8gb|code-block|syntax|javascript|1448578|https://medium.com/@vuongtran/how-to-solve-process-out-of-memory-in-node-js-5f0de8f8464c|1448579|entityMap|0|LINK|mutability|MUTABLE|url^0|26|K|0|0|0|2G|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|W|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|X|8|@]|D|@$9|Y|A|Z|1|10]]|E|$]]|$1|M|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|L]]]]

This error occurs when the memory allocated for the executing application is less than the required memory.
By default, the memory limit in Node.js is 512 MB. To increase this amount, you need to set the memory limit argument <code>—-max-old-space-size</code>. It will help avoid a memory limit issue.
<pre><code>node --max-old-space-size=1024 index.js #increase to 1gb
node --max-old-space-size=2048 index.js #increase to 2gb
node --max-old-space-size=3072 index.js #increase to 3gb
node --max-old-space-size=4096 index.js #increase to 4gb
node --max-old-space-size=5120 index.js #increase to 5gb
node --max-old-space-size=6144 index.js #increase to 6gb
node --max-old-space-size=7168 index.js #increase to 7gb
node --max-old-space-size=8192 index.js #increase to 8gb
</code></pre>
<a href="https://medium.com/@vuongtran/how-to-solve-process-out-of-memory-in-node-js-5f0de8f8464c" rel="noreferrer">https://medium.com/@vuongtran/how-to-solve-process-out-of-memory-in-node-js-5f0de8f8464c</a>

blocks|key|725694|text|2020更新|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|725695|这些选项是现在由节点正式记录。对于2GB的机器，您可能应该使用：|725696|NODE_OPTIONS=--max-old-space-size=1536|code-block|syntax|javascript|725697|确定要使用的金额|725698|您可以使用free+-m在Linux机器上看到可用内存。请注意，您可以将free和buffers/cache内存的总数考虑为可用的，因为buffers/cache可以在需要时立即丢弃(这些缓冲区和缓存是使用其他未使用内存的好方法)。|CODE|725699|max-old-space-size还提到：|725700|在内存为2GB的计算机上，考虑将其设置为1536+(1.5GB)|blockquote|725701|因此，上述价值。考虑到基本操作系统所需的内存量并没有太大的变化，所以您可以很高兴地在一台4GB的机器上完成3.5。|725702|要注意默认值并查看更改的效果：|725703|缺省值为2GB：|725704|$+node

>+v8.getHeapStatistics()
{
++....
++heap_size_limit:+2197815296,
}|725705|2197815296是2GB字节。|725706|当设置为8GB时，您可以看到heap_size_limit更改：|725707|$+NODE_OPTIONS=--max_old_space_size=8192+node
Welcome+to+Node.js+v14.17.4.
Type+".help"+for+more+information.
>+v8.getHeapStatistics()
{
++...
++heap_size_limit:+8640266240,
++...
}|725708|正如@Venryx下面提到的，您也可以使用process.memoryUsage()|725709|entityMap|0|LINK|mutability|MUTABLE|url|https://nodejs.org/api/cli.html#cli_node_options_options|1|https://nodejs.org/api/cli.html#cli_max_old_space_size_size_in_megabytes|2|https://nodejs.org/api/process.html#processmemoryusage^0|0|6|0|5|9|0|0|0|0|5|7|10|4|15|D|1W|D|0|0|I|0|I|1|0|0|0|0|0|0|0|E|F|0|0|L|L|2|0^^$0|@$1|2|3|4|5|6|7|1O|8|@$9|1P|A|1Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1R|8|@]|D|@$9|1S|A|1T|1|1U]]|E|$]]|$1|H|3|I|5|J|7|1V|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1W|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|1X|8|@$9|1Y|A|1Z|B|Q]|$9|20|A|21|B|Q]|$9|22|A|23|B|Q]|$9|24|A|25|B|Q]]|D|@]|E|$]]|$1|R|3|S|5|6|7|26|8|@$9|27|A|28|B|Q]]|D|@$9|29|A|2A|1|2B]]|E|$]]|$1|T|3|U|5|V|7|2C|8|@]|D|@]|E|$]]|$1|W|3|X|5|6|7|2D|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|2E|8|@]|D|@]|E|$]]|$1|10|3|11|5|6|7|2F|8|@]|D|@]|E|$]]|$1|12|3|13|5|J|7|2G|8|@]|D|@]|E|$K|L]]|$1|14|3|15|5|6|7|2H|8|@]|D|@]|E|$]]|$1|16|3|17|5|6|7|2I|8|@$9|2J|A|2K|B|Q]]|D|@]|E|$]]|$1|18|3|19|5|J|7|2L|8|@]|D|@]|E|$K|L]]|$1|1A|3|1B|5|6|7|2M|8|@]|D|@$9|2N|A|2O|1|2P]]|E|$]]|$1|1C|3|-4|5|6|7|2Q|8|@]|D|@]|E|$]]]|1D|$1E|$5|1F|1G|1H|E|$1I|1J]]|1K|$5|1F|1G|1H|E|$1I|1L]]|1M|$5|1F|1G|1H|E|$1I|1N]]]]

<h2>2020 Update</h2>
These options are <a href="https://nodejs.org/api/cli.html#cli_node_options_options" rel="noreferrer">now documented officially by node</a>. For a 2GB machine, you should probably use:
<pre><code>NODE_OPTIONS=--max-old-space-size=1536
</code></pre>
<h2>To determine the amount to use</h2>
You can see available memory on a Linux machine using <code>free -m</code>. Note that you can consider the total of the <code>free</code> and the <code>buffers/cache</code> memory as available, as <code>buffers/cache</code> can be thrown away instantly when needed (these buffers and cache are a nice way to use otherwise unused memory).
The <a href="https://nodejs.org/api/cli.html#cli_max_old_space_size_size_in_megabytes" rel="noreferrer">official documentation for<code>max-old-space-size</code></a> also mentions:
<blockquote>
On a machine with 2GB of memory, consider setting this to 1536 (1.5GB)
</blockquote>
Hence the value above. Consider that the amount of memory needed for the base OS doesn't change much, so you could happily do 3.5 on a 4GB machine etc.
<h2>To notice the defaults and see the effect of changes:</h2>
The default is 2GB:
<pre><code>$ node

&gt; v8.getHeapStatistics()
{
 ....
 heap_size_limit: 2197815296,
}
</code></pre>
2197815296 is 2GB in bytes.
When set to 8GB, you can see <code>heap_size_limit</code> changes:
<pre><code>$ NODE_OPTIONS=--max_old_space_size=8192 node
Welcome to Node.js v14.17.4.
Type &quot;.help&quot; for more information.
&gt; v8.getHeapStatistics()
{
 ...
 heap_size_limit: 8640266240,
 ...
}
</code></pre>
As @Venryx mentions below you can also use <a href="https://nodejs.org/api/process.html#processmemoryusage" rel="noreferrer">process.memoryUsage()</a>

blocks|key|725711|text|对我来说，当内存消耗接近2GB时，Azure函数调用在7GB实例中终止，并带有以下错误消息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|725712|Exception+while+executing+function:+Functions.graphql-mobile+node+exited+with+code+134
+[24164:000001CE2EB5CF00]+10557962+ms:+Scavenge+(reduce)+2041.0+(2050.5)+->+2040.1+(2051.5)+MB,+2.3+/+0.1+ms++(average+mu+=+0.179,+current+mu+=+0.002)+allocation+failure+,FATAL+ERROR:+Ineffective+mark-compacts+near+heap+limit+Allocation+failed+-+JavaScript+heap+out+of+memory,+3:+00007FF73E006026+node::OnFatalError%2B294+|code-block|syntax|javascript|725713|我通过在我的应用程序设置中设置最大旧空间大小来解决这个问题。|725714|"languageWorkers:node:arguments":+"--max-old-space-size=5500"|725715|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

For me, Azure function invocations was terminating in a 7GB instance when the memory consumption is near to 2GB with the following error message.
<pre><code>Exception while executing function: Functions.graphql-mobile node exited with code 134
 [24164:000001CE2EB5CF00] 10557962 ms: Scavenge (reduce) 2041.0 (2050.5) -&gt; 2040.1 (2051.5) MB, 2.3 / 0.1 ms (average mu = 0.179, current mu = 0.002) allocation failure ,FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory, 3: 00007FF73E006026 node::OnFatalError+294 
</code></pre>
I solved the issue by setting max-old-space-size like this in my application settings
<pre><code>&quot;languageWorkers:node:arguments&quot;: &quot;--max-old-space-size=5500&quot;
</code></pre>

I'm having some trouble to understand how Node.js acts based on the parameter <code>max-old-space-size</code>.
In my case, for example, I'm running two <code>t2.small</code> AWS instances (2GB of RAM).
Not sure why, but I did set <code>max-old-space-size=4096</code> (4GB). What does node do in this case? Could this configuration lead to a possible memory allocation failure?
How do I determine the correct value of <code>max-old-space-size</code> based on the server resources?
My application is constantly growing the memory usage and I'm trying to understand everything about node internals.

How do I determine the correct "max-old-space-size" for node.js?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我很难理解Node.js是如何基于参数max-old-space-size工作的。例如，在我的例子中，我运行两个t2.small AWS实例(2GB内存)。不知道为什么，但我确实设置了max-old-space-size=4096 (4GB)。在这种情况下节点是做什么的？这种配置会导致内存分配失败吗？如何根据服务器资源...

问如何为node.js确定正确的“最大旧空间大小”？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何为node.js确定正确的“最大旧空间大小”？EN