It is more the Firefox load that I am showing which is running on the NUC. (The bigger machine - 192.168.0.6)
Which in the first screen shot is showing 86.94.
I guess in retrospect it should/could have been more "FireFox CPU load. . . . ."
But it is only tabs in FireFox with are dealing with Node-Red which are getting such spikes.
They may last for a couple of seconds or they may last . . . . . . an annoyingly long time.
Not to be confused with a "REBOOT annoyingly long time".
I didn't know of the firefox taskmanager and was told of it only recently.
I'm monitoring it and created this more to help (show?) other people who may have similar problems that they are not alone.
Granted: having 30 "sessions" of Firefox won't help.
I'm not even going to have at a guess how many tabs.
It is just it happens now and then and for no particular reason.
None of the remote machines running node-red are straining. Granted there are spikes when they do their cycles but that is only for maybe a second at most. But for the main one where it could last 8 seconds as it pings, and does other stuff.
But it is not always that machine's node-red which is maxing out this machine's Fire fox. It could even be Node-red on this machine.
I really can't see anything which could cause it.
Again: I am mentioning it so if others have the problem....... (De ja vous)
Does that help?
