You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On "small devices" (e.g. Raspi, Banana Pi), page loading takes "ages" – most likely as the graphs are created on request, and only sent to the browser once they're all complete. I'd suggest two possible improvements:
give each graph/section a link/switch to just reload that one (I often find myself in the situation where the page was already opened a while ago, an I just need to re-check a single graph – so reloading only that one would suffice, no need to reload everything)
start "sending" each section as soon as it's done (instead of sending all together once the entire preparation is done)
Optionally, make that configurable (as it might be no issue on "big systems").
The text was updated successfully, but these errors were encountered:
Thanks, that's a start. Still, with 20+ graphs on a "low-spec" device (think: RasPi, BananaPi) it won't help that much – especially for single-core devices. On my BananaPi (DualCore) it should speed up things by ~50..75%. Still, often it's a specific graph one needs to refresh without being interested in all the others, so a "reload" link on each (as described in my initial post) would be much appreciated.
With this option, you might include the RRDtool option called --lazyRRDtool documentation which, as documentation says, Only generate the graph if the current graph is out of date or not existent.
On "small devices" (e.g. Raspi, Banana Pi), page loading takes "ages" – most likely as the graphs are created on request, and only sent to the browser once they're all complete. I'd suggest two possible improvements:
Optionally, make that configurable (as it might be no issue on "big systems").
The text was updated successfully, but these errors were encountered: