Hi again, In past I had quite a lot of problems (which I thought I solved) with consuming too much memory (running out of heap memory). After understanding that all the graphs that I was generating ended up eating all available memory. Since then I have started using Influxdb (V2/Flux) and transferr…

Not quite clear - is Node-RED running on the tablet as well as the browser? If not, where is Node-RED running? Also, I assume you are using other features of FlexDash, not just embedding Graphana in it? If not, that is a lot of overheads for no gain. Indeed, since Grafana is web-based, would it not…

Hi Julian, Apologies not been clear enough. The Node Red is running on a dedicated Ubuntu 20.04 LTS. On the server side I do not have any issues. It is really more the android tablet side I do see the issues now. My understanding was as the current dashboard (3.5.0) is a SPA I needed to off load s…

[image] Soiski: My understanding was that as Flexdash sits in a different address these frames would not be loaded as part of the SPA to the tablets when initiating the normal dashboard (3.5.0). So hence I have created following Flexdash pages . [image] Soiski: Has my understanding been …

Thanks for insight. I have now removed Flexdash and incorporated direct links to grafana (though still in iFrame link in tab), hence moving a little bit of overhead from my node red setup. Lets see if that helped in any significant way. Eagerly waiting for the new dashboard version to grow from alp…

Maybe try out uibuilder while you are waiting. :wink: You never know, it might be ideal for your use.

I'm confused by your description of the problem. You show graphs about memory usage in NodeRED, which is on the server and at the same time you write about memory usage on android tablets. Those are completely unrelated things... If you're just using FlexDash to embed Grafana then that's indeed not…

[image] tve: Influx with Flux It also negates the benefit of using InfluxDB with Grafana since I don't think you can use the point-and-click query builder any more.

Hi tve, Thanks for your comments let me try to unconfuse you ( long post but please read it through). So my journey with node-red start really from version one long time ago when I built my first nodemcu arduino boards to measure temperature originally inside my house. Node Red was new and ideal on…

[image] Soiski: my two separte android tablets ( that are typically showing these screens; out of total 18 pages/tabs) where reloading (from scratch) the screens Please explain exactly what you mean by reloading the screens. Also do both tablets do it at the same time?

Hi Colin, Happens typically same time for both screen (even though presenting different pages). I guess this is due SPA model. Like for the 1st screen the pages flashes totally black (or background grey) and the values are missing for a second. Then they reload to last values. The bottom right wh…

Node-RED

Node-RED Forum

Node Red memory consumption / "leak" affecting android tablets

General

system Closed 20 October 2023 13:28 15

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Memory leak ?... trouble performance now General	36	2466	13 February 2022
Memory usage grows steadily General	33	510	13 July 2025
Memory problem Dashboard/plotly.js Dashboard	26	1981	26 March 2021
Memory leakage with simple dashboard Dashboard	17	954	17 May 2020
Unplanned Restart / Reboot? General	45	3152	27 April 2020

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Node Red memory consumption / "leak" affecting android tablets

Related topics