On Tue, 16 Jan 2018 12:02:04 -0500, Dennis Lee Bieber wrote:

> Your browser is eating >100% (being a four-core processor, 100% means
> all of one core). Uh, and you seem to have two browser processes running
> and between them they are eating a quarter of your memory (though that
> may just mean Chromium runs a master process and an additional process
> per open tab; I don't have the experience to tell).
>
The URL posted by Richard says that Chromium has a master process
handling the main screen and supervisory functions plus one process per
tab.

That had me scratching my head for exactly the same reasons as you when I
saw two processes, both called Chromium, until he posted that link: I
know that the Java jvm is a multi-threaded single task and always shows
up as a single line in the 'top' process list.

> Node-Red itself is not using much (though it is using a touch
> more than the X-window system task). In truth -- at the time of
> that screen grab, node-red is in a blocked/sleep state, doing nothing.
>
Yesterday I found description of Node-red internals:
https://en.wikipedia.org/wiki/Node.js

The gory details are the the "Technical details" section.

Summarising, this says Node-red is written in Node.js Javascript. This
runs as compiled machine code generated by Google's V8 runtime package.
The control and management code runs as a single thread using non-
blocking i/o. I/O requests are added to an event queue which is serviced
by a thread pool and uses a call-back mechanism to activate the modules
defined via the Node-red flow editor. The non-blocking i/o, event queue
and thread pool components are all part of the libuv library, which also
supports a mechanism for increasing the size of the thread pool from its
default value of one.

> For comparison purposes (since you stated remoting in with the browser
> running on another computer doesn't show the problem): set up the same
> run as captured here, but do not run the browser locally. Use the remote
> browser. Then capture the TOP output on the RPI again. Without the
> browser hog on the RPI, I expect you'll see total CPU% down around
> 5-10%, or even lower.
>
Yes: good advice.


--
Martin    | martin at
Gregorie  | gregorie dot org

--- SoupGate-Win32 v1.05