We upgraded Grafana in one of our environments from Grafana v3.1.1 (commit: a4d2708) to Grafana v4.3.1 (commit: befc15c). We are hitting InfluxDB version 1.0.2 as the data source. Did something change on the order of how graphs are rendered? In the old version it seemed that all graphs rendered all at once, which was great. In the new version, I noticed that graphs only seem to render when they are visible in the browser. Some of our dashboards are full of lots of graphs, so it takes a long time to scroll through them and see everything get rendered. I can sort of work around this by zooming my browser window out as far as it will go to make most charts visible, but that is of course a bit silly. Is there an option for getting the old behavior back?
Thanks. (Sorry if this was asked before. I did try searching for this topic before asking, but came up dry.)
I think my post can be ignored. I just saw this in the release notes for v4.3.2:
Lazy Loading Of Panels: Panels are no longer loaded as they are scrolled into view, this was reverted due to Chrome bug, might be reintroduced when Chrome fixes it’s JS blocking behavior on scroll. #8500
I’m assuming that that will fix the issue I’m seeing, so we’ll upgrade to v4.3.2 and check again. The comment suggests that this change might be introduced again. I guess as long as we don’t see the same behavior in the future we’ll be happy. Thanks.
Lazy loading of panels got introduced in 4.3.0 but got reverted in 4.3.2 due to a Chrome bug.
From the changelog:
In version 4.3.0:
Panels: Delay loading & Lazy load panels as they become visible (scrolled into view) #5216
In version 4.3.2:
Lazy Loading Of Panels: Panels are no longer loaded as they are scrolled into view, this was reverted due to Chrome bug, might be reintroduced when Chrome fixes it’s JS blocking behavior on scroll. #8500
Thanks. Yeah, I found that within minutes after my initial post. (Had I studied the release notes prior to posting, I would have caught myself. Ah well.)
If the Lazy Loading feature is indeed ever reintroduced, I hope that an option is added for disabling it, with the default set to the current behavior. I’d frankly prefer to have our data sources take the hit on any extra load on them that would occur without the lazy loading, as opposed to our end users. Thanks.
