On Sun, 14 Jan 2018 10:32:05 -0500, Dennis Lee Bieber wrote:

> I'm still of the opinion that the problem is in the CPU usage of
> the monitoring program
>
You may well be right. I know nothing about Node-red except for a quick
look at its Wikipedia entry, which says that it is written in node.js, is
single threaded and uses async i/o.

I wasn't trying to solve the OPs problem directly. He doesn't seem all
that familiar with the 'top' utility, so I thought a micro-tutorial on it
might be in order, especially since its manpage is quite long.

> So -- I'd consider noting the %CPU column and the associated
> process/command... A partial grab (from a Debian install running in
> VirtualBox -- USE FIXED PITCH FONT TO VIEW):
>
Good point, though it seems as though the node.js runtime should be at
least as efficient as the Java jvm, provided that V8 generates code of
similar efficiency to javac + the jvm's JIT compiler.


--
Martin    | martin at
Gregorie  | gregorie dot org

--- SoupGate-Win32 v1.05