-
-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: High and increasing CPU usage over time #505
Comments
Hey, behaviour is unknown to me. Running node for years and have never seen it. Can you tell me more about the setup? |
What about machine specs? |
Pi 4B 4GB, running Node-RED under docker |
To me sounds like an infinity loop. |
no i can guarantee that is not the case, because as i said, i manually checked every input and output of the nrchkb nodes, and there is nothing wrong, no spam or looping messages. |
I am on version 3. Do you mind to share your flow? |
|
NR 3.0.2 |
same problem after updating 1.4.x -> 1.5.0, no new scripts or changes NR 3.0.2, intel nuc, 8gb ram, but NR is almost dead after 2-3 days, high cpu load only restart nodered.service can help for a few days how to debug this? |
First of all, you can run nodered with debug mode. DEBUG=* |
OK, reverted to 1.4.3 but still have a problem. And it looks like a different problem. Sometimes pressing a button in a home.app (on any device, even ATV in local wifi) causes a 3-10 sec hanging before a "signal" is caught by NR node. Direct inject/debug works immediately, but home.app (and all it automations of course) clicks makes it hangs sometimes. https://idiod.video/v14knh.mp4 — you can notice a circle sometimes after clicking Rebooting, restarting and so on, no idea even how to start to debug this. No trails in NR logs, looks like it just delaying commands sometimes. |
I don’t use Docker so might be unrelated. |
@ptath where did you get with this? |
NRCHKB Plugin Version
1.4.3
Node JS Version
3.0.2 Node-RED Container
NPM Version
3.0.2 Node-RED Container
Node-RED Version
3.0.2
Operating System
Docker
What happened?
The CPU usage of Node-RED is super high, and incresaing day by day. It happened 2 times that it reached a point where Node-RED was running 5 seconds late on every message, and CPU usage was pinned at 100%. I traced down the issue, and it's NRCHKB. Never had this issue, and I don't precisely know when it started. Probably did a palette update, but din't pay attention to what version i was running before. The flows haven't changed.
I restarted Node-RED yesterday evening, and it was at 25% usage.
It now was at 50%, so i tried disabling the bridge configuration nodes, and the usage went down to 0%. Then i re-enabled the bridges and the usage went up to ~25%.
Here a pic during this process. Node-RED stats in portainer
I checked all NRCHKB nodes to see if maybe something is spamming messages in the nodes, but it's all OK.
The strange thing i think is the fact that the usage keeps increasing and increasing, up to a point where Node-RED becomes so slow that it needs a restart.
I'm running on a Pi 4B, under docker
Is this a known behavior?
Thanks!
How to reproduce?
Nothing particular
Expected behavior:
Describe expected behavior here, with relevant screenshots if they would help.
Additional comments?
Additional comments here, if any.
Relevant log output
There are no logs from NRCHKB in Node-RED logs.
The text was updated successfully, but these errors were encountered: