I’m afraid I don’t have much insight to offer into it since I just inherited the management of the app, and mostly just contributed to adding chart types which was limited to API call formation. But what I can say is:
(1) you may want to post in the Quick Chart thread to see if anyone else has a similar situation with a corresponding suggestion. It may just be related to how you've set it up, e.g., how many data points you're capturing, with how many devices, to file or no file, etc. I am using a lot of charts and don't have memory issues, but i may be charting different stuff than you in different ways. I will say that +7 days of data is a lot of data to keep around and that may very well be the memory hog.
(2) I myself am starting to look at external graphing solutions like Grafana, not because of any issues I've had with Quick Chart, but because it is, in the end, the better solution if you can devote the time, energy, resources, and complexity to it....
2 Likes
Could look at [BETA] CSV Visualization - Completely Local Data Graphs as another option.
1 Like
This.
The hub wasn’t designed for this task, so it’s potentially easy to configure a logging and/or charting app in a way that will degrade hub performance.
Not suggesting that must be the explanation in OP’s case, but IMO that should always be the first thing that gets ruled out in a situation like this.
