Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Node-RED-docker causes regular CPU spikes

未关闭
#293 7 条评论 2 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
docker, node.js

调研方向

首先,使用全新的 nodered/node-red:latest (2.1.3) 容器重现该问题,并按照报告中的说明使用 docker stats 对其进行监控。比较存在和不存在活动流及第三方库时的行为;完成的标准是确定反复出现的 30-minute CPU spike 的原因,并确认该现象不再发生。

由索引模型根据 Issue 内容生成。

描述

I have recently noticed that a closely monitored docker container using image nodered/node-red:latest (2.1.3) shows, on the processor core (or thread ?) it uses, CPU spikes up to 100% every 30 minutes. My monitoring happens by polling docker stats regularly and graphing it over time. This also occurs if the container is fresh, i.e. with no active flows, no third-party libraries installed, no custom code, etc.

Node-RED CPU spike behavior

A fuller writeup, with many helpful comments from community members, is available on the Node-RED Forum. When reading through it, bear in mind that the suspicion that Node-RED crashed my system was false.

A quick summary of the salient findings:

  • other Node.js containers on my system do not show these spikes.
  • manually inserted GC calls do not mitigate the issue, making it unlikely to be related to Node.js GC
  • other users can reproduce spikes, whether they're on Docker or not

Given the replies and confirmations that the issue was reproducible, I believe that my environment is irrelevant, but here goes: I am running on a system with an Intel Celeron N3350 processor with 4GB of memory. The OS is Ubuntu 20.04 LTS and I am running Docker version 19.03.8, build afacb8b7f0.

主要语言
Shell
星标
540
派生
434
平均合并
24 分钟
30 天内合并 PR
5

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

node-red/node-red-docker 的其他 Issue

查看 node-red/node-red-docker 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。