Node-RED-docker causes regular CPU spikes
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, node.js
- Domain
- devops, infrastructure
Research direction
Start by reproducing the issue with a fresh nodered/node-red:latest (2.1.3) container and monitor it using docker stats, as described in the report. Compare the behavior with and without active flows and third-party libraries; done means identifying the cause of the recurring 30-minute CPU spike and confirming that it no longer occurs.
Written by the indexing model from the issue text.
Description
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.
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.
- Dominant language
- Shell
- Stars
- 540
- Forks
- 434
- Avg merge
- 24m
- Merged PRs (30d)
- 5
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from node-red/node-red-docker
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
node-red/node-red-docker#536 ·
-
node-red/node-red-docker#522 · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
node-red/node-red-docker#513 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
node-red/node-red-docker#510 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
node-red/node-red-docker#493 · 13 comments ·
All issues in node-red/node-red-docker
Similar issues
-
Issue-Enhancement Needs-Triage
Difficulty 1/5 Under an hour Newbie friendliness 86/100
PowerShell/PowerShell#28061 · 2 reactions ·
-
Feature Request: Add ability to load custom environment variables in linux-exec-server-installer.sh Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
microsoft/vscode-remote-release#11867 ·
-
AuTest Bug Tests
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/trafficserver#13714 ·
-
Update to NCCL 2.32 Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
conda-forge/nccl-feedstock#166 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
vllm-project/agentic-api#358 · 1 comment ·