After updating to 2025.2 graphs that have bit more data are very slow to read values when pointing with cursor. It takes few seconds for each update. Graphs with less data work well.
I tested Firefox and Edge both behave similarly.
Loading time for graph when opening page is normal and page it self scrolls normally.
Issue is only with mouse over for actual values.
Does anyone else have similar issue?
Same issue, a lot slower, and also lost the ability to zoom in the graph using CTRL and drag click. It crashes on the browser too.
Ok I figured out the issue, I was using history graph card instead of statistic graph card. The history graph shows ALL the data points which is taxing on the system. Switch all the graph to statistic chart and solved the lag issue.
However I the control zoom feature on graph is no longer exists it seems.
You have not solved the issue.
You merely switched to another card.
Same problem for me, history graph card and the history panel has become incredibly slow, especially when zooming.
I have also the problem to the point that some of my pages are becoming impossible to use on the android app (they are slow on the computer but seems even worse on the android app).
Same here. Since 2025.2 both the app and the website are so slow, almost unusable. 
Same issue with my system.
Annoyingly slow graph performance (and unnecessary animation slowdowns) since 2025.2.2.
Server is powerful enough 32G RAM, 12th Gen 4.4GHz i5, Debian 6.5, MariaDB
Desktop: 32G RAM, i5 10400F, W10
Phone: Galaxy S24
None of the above is junk hardware, and everything changed with 2025.2.2 update, everything was fine before this update.
I think it is wise to create an issue on Github because it is not likely the developer will see it here. When doing so, more informations is needed though.
Since not everyone is experiencing the same issue, the dev will need to figure out what the difference for you is. Since it is a frontend change, most likely is that the browser and device are more relevant info than the server hardware. Also screenshots could help, or more details about the types of sensors you display.
Needs more attention.
That PR for that issue is merged 4 days ago, not sure if it’s already in the new release?
It was in the new release. Working fine for me 