On Tue, 16 Jan 2018 19:07:52 -0800, Dannaz Perth wrote:

> Hello Chaps.
>
> Thanks for the feedback. I was also under the conclusion the memory draw
> was massive when loading Chromium.
> The problem i'm having is not just with Chromium. It happens on every
> browser app i install.
> Below is a screen shot using, Vivaldi. FireFox, LuaKit do the exact
> same.
> It is almost like it cannot handle the Graphics or java used to drive
> the program nodes.
> Is there a way of to determine this. I also followed some tuning tips
> for Chromium. basically using the web settings page and turning things
> on and off.
>
> https://pasteboard.co/H3hkYDy.png
>
> Surely this can be fixed ?
>
Maybe not. IIRC Node-red uses JSON to communicate with other processes,
which implies that there's quite a large lump of JavaScript running on
the web browser to convert messages from Node-red into a graphical
display. This obviously consumes CPU cycles, reinforcing the idea that
running the browser remotely on a more powerful host is the way to go.

BTW I don't see why you don't like this approach, which works really well
here: I do almost everything from this laptop, connecting via SSH to my
house server or my RPi as needed. All machines have SSH configured for X11
forwarding, so I can sit in front of anything with an attached screen and
run both command line and graphical programs on anything else on my
network, including the ADSL router.


--
Martin    | martin at
Gregorie  | gregorie dot org

--- SoupGate-Win32 v1.05