nodejs v8内存gc分配失败

我试图用一个什么都不做的服务器来configurationnodejs v8内存。 我使用节点memwatch来获取堆差异。 在连接和连接closures之前,我收集堆信息。 我用节点memwatch。 我尝试从客户端200并发连接。

这是连接撕下后的gc轨迹。

谁能帮我理解:

为什么记忆力在​​增加? 在连接断开之后,服务器绝对没有任何作用。 它不应该总是下降,因为垃圾收集
2.这些分配失败是什么? 我如何真正解释这里的痕迹?

15802 ms: Mark-sweep 8.9 (45.0) -> 8.1 (45.0) MB, 58 ms [allocation failure] [GC in old space forced by flags]. 16144 ms: Mark-sweep 9.2 (45.0) -> 8.4 (45.0) MB, 53 ms [allocation failure] [GC in old space forced by flags]. 16495 ms: Mark-sweep 9.5 (45.0) -> 8.7 (46.0) MB, 60 ms [allocation failure] [GC in old space forced by flags]. 16837 ms: Mark-sweep 9.8 (46.0) -> 9.0 (46.0) MB, 56 ms [allocation failure] [GC in old space forced by flags]. 17197 ms: Mark-sweep 10.1 (46.0) -> 9.4 (46.0) MB, 62 ms [allocation failure] [GC in old space forced by flags]. 17905 ms: Mark-sweep 11.5 (46.0) -> 10.0 (47.0) MB, 74 ms [Runtime::PerformGC] [GC in old space forced by flags]. 18596 ms: Mark-sweep 12.2 (47.0) -> 10.7 (47.0) MB, 75 ms [Runtime::PerformGC] [GC in old space forced by flags]. 19315 ms: Mark-sweep 12.8 (47.0) -> 11.3 (48.0) MB, 83 ms [allocation failure] [GC in old space forced by flags]. 20035 ms: Mark-sweep 13.4 (48.0) -> 12.0 (49.0) MB, 90 ms [Runtime::PerformGC] [GC in old space forced by flags]. 21487 ms: Mark-sweep 16.0 (49.0) -> 13.2 (50.0) MB, 96 ms [Runtime::PerformGC] [GC in old space forced by flags]. 22950 ms: Mark-sweep 17.3 (50.0) -> 14.5 (52.0) MB, 116 ms [Runtime::PerformGC] [GC in old space forced by flags]. 24376 ms: Mark-sweep 18.8 (52.0) -> 15.9 (53.0) MB, 114 ms [allocation failure] [GC in old space forced by flags]. 25849 ms: Mark-sweep 19.9 (53.0) -> 17.2 (54.0) MB, 129 ms [Runtime::PerformGC] [GC in old space forced by flags]. 28773 ms: Mark-sweep 25.2 (54.0) -> 19.7 (57.0) MB, 149 ms [allocation failure] [GC in old space forced by flags]. 31725 ms: Mark-sweep 27.7 (57.0) -> 22.2 (59.0) MB, 172 ms [Runtime::PerformGC] [GC in old space forced by flags]. 34678 ms: Mark-sweep 30.2 (59.0) -> 24.7 (61.0) MB, 190 ms [Runtime::PerformGC] [GC in old space forced by flags]. 44045 ms: Mark-sweep 28.4 (61.0) -> 25.8 (63.0) MB, 180 ms [idle notification] [GC in old space forced by flags]. 44216 ms: Mark-sweep 25.8 (63.0) -> 25.8 (63.0) MB, 170 ms [idle notification] [GC in old space requested]. 57471 ms: Mark-sweep 26.9 (63.0) -> 25.8 (62.0) MB, 167 ms [Runtime::PerformGC] [GC in old space forced by flags]. 57651 ms: Mark-sweep 26.8 (62.0) -> 25.5 (62.0) MB, 160 ms [Runtime::PerformGC] [GC in old space forced by flags]. 57828 ms: Mark-sweep 26.5 (62.0) -> 25.5 (62.0) MB, 159 ms [Runtime::PerformGC] [GC in old space forced by flags]. 

谢谢,

       

网上收集的解决方案 "nodejs v8内存gc分配失败"

“分配失败”听起来非常戏剧化,但并没有涉及真正的失败。 这只是意味着我们分配了太多内存,现在是时候做一个GC来看看我们是否可以收集一些内存。

看起来你正在用–gc-global标志(“GC被标志强制”)运行。 对于生产来说这是一个坏主意,尽pipe在debugging时缩小问题可能没有问题。

我不知道为什么你的过程泄漏。 您可能会发现堆分析器很有用。 请参阅https://github.com/felixge/node-memory-leak-tutorial

根据代码:

 PrintF("%s %.1f (%.1f) -> %.1f (%.1f) MB, ", CollectorString(), static_cast<double>(start_object_size_) / MB, static_cast<double>(start_memory_size_) / MB, SizeOfHeapObjects(), end_memory_size_mb); 

每行都是一个gc,当gc开始时,

 start_object_size_ = heap_->SizeOfObjects(); 

在gc总结中:

 PrintF("total_size_before=%" V8_PTR_PREFIX "d ", start_object_size_); PrintF("total_size_after=%" V8_PTR_PREFIX "d ", heap_->SizeOfObjects()); 

至于为什么start_object_size_在我的应用程序闲置的时候增加,我猜测可能在gc期间,一些对象被提升到旧空间,并导致旧空间中的对象大小增加。