pi node-red (15.2) goes 100% after a number of deploys
119 views
Skip to first unread message
Simon H
unread,
Jan 15, 2017, 3:50:53 PM1/15/17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Node-RED
Does anyone else find that after a few deploys (I always do a 'full' deploy), that after each deploy node-red cpu usage rises, until each deploy takes longer and longer, and eventually node-red is sitting close to 100% cpu; solved by killing it and letting it restart?
I thought it might have been gathering graph data, but I'm limiting the number of points, and the CPU seems to be ok for days if i'm not working on flows, so i'm pretty convinced it's related to deploys....
I have 10 flows, non std nodes include wemo, bigtimer (issues occurred before installation of this one), all other nodes are std (mqtt, various dashboard, function nodes, inject, etc.).
Is there an easy way to profile what's going on? I've used node-debug on windows, but don't really fancy this on pi. Maybe some way to dump the nodejs task queue on demand?
Any thoughts welcome.
s
Colin Law
unread,
Jan 15, 2017, 5:07:27 PM1/15/17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to node...@googlegroups.com
I am not seeing increased cpu usage (that I have noticed), but on one
of my Pis every time I deploy it uses more memory, till eventually the
whole thing grinds more or less to a halt and I have to restart
node-red, if it does not crash and restart itself. I have not reported
it as the flow includes DIY charts and it may be something I am doing
that is causing the problem so I was going to do a bit of
investigation first.
Colin
On 15 January 2017 at 20:50, 'Simon H' via Node-RED