SLOW graph rendering with chrome

[GlueGuy]

Context: Windows 8.1 x64
Chrome: 41.0.2272.76
Firefox: 35.0

Over the last week, I've been seeing long delays when rendering graphs in chrome. This only seems to affect graph rendering, and only in chrome. So I suspect there is something about the way that rrdtool renders the graphs that is getting chrome's knickers in a twist. When I run cacti in firefox or IE, the delays do not occur, and it's only been happening for about the last week.

I've turned off all extensions, and cut chrome down to the basics. Just wondering if anyone else is seeing this problem?

[BSOD2600]

Chrome is my daily browser and I dont notice any problems.

[GlueGuy]

Then what would it be? I've tried it on both firefox and IE, and they are both sub-1-second response.

Chrome mostly is too, until I try to display graphs. i then get these 20-30-40 second delays. So there is definitely something wrong with chrome in this regard.

[cigamit]

Chrome is my daily browser also, and I haven't had any issues. In Chrome, you can go to the developer tools and then the network tab and see if anything is abnormal there when it is loading the images.

[GlueGuy]

I can see that it's using quite a lot more processor power than the equivalent operation in firefox. The graphs below show the same operation in firefox and chrome. Firefox barely makes a blip on CPU usage, but chrome goes 35-40% busy for about 24 seconds (on this example). It's sometimes even slower.

[GlueGuy]

Took a snapshot with the suggested developer's tool. Seems to be spending all it's time writing. About 19.4 seconds in this instance.

[BSOD2600]

How many items are in the graph tree? ftiens4.js is related to the tree code (which has since been overhauled in the current alpha release). Did a cpu profile in Chrome with 30 graphs and ftiens4.js wasnt among the top consumers for me.
Found this too from years ago: http://forums.cacti.net/viewtopic.php?f=21&t=34712

[GlueGuy]

How many items are in the graph tree? ftiens4.js is related to the tree code (which has since been overhauled in the current alpha release). Did a cpu profile in Chrome with 30 graphs and ftiens4.js wasnt among the top consumers for me.

Meaning the number of items in the tree, or the number of graphs on the node of the tree?

Most of the nodes have between 7 and 12 graphs on the tree node. The graph trees that I've been looking at have between 6 and 40 elements in the tree.

Just wondering if maybe something is just broken in my copy of chrome. Perhaps I should un-install/re-install chrome to see if it changes anything? My installation of chrome is fairly vanilla; I don't really load up on extensions or anything. In fact, I have shockwave/flash installed (which I think is not an extension), plus an extension for Google drive (which I recently installed). And that's it.

Code: Select all

Update 10 March 2015

I removed the google drive extension; no change.

[GlueGuy]

I tested it on two different machines. One is an old Windows XP machine, and it displayed the same problem. Then ran it on my wife's Windows 7 machine. It runs normally on that one.

So this only affects some machines. I have no idea how to figure out what the issue is . In the mean time, I guess I will only run cacti on firefox or IE.

[GlueGuy]

I did some poking around and it seems that this ftiens4.js has been around a long time. All of them seem to be > 10 years old, but they are not the same (even though the comments all look the same). I downloaded one from Sourceforge, and it is quite different in several areas (see below). I ran a diff, and there are more than a dozen differences, but the comments about changes are identical.

Code: Select all

-rw-r--r-- 1 apache apache 29586 Apr  3  2012 ftiens4.js
-rw-r--r-- 1 root   root   30348 Mar 10 18:16 new_ftiens4.js

[GlueGuy]

looks like a non-issue if I just upgrade to 0.8.8c. Notes from the 0.8.8c changelog:

Code: Select all

bug#0002228: GPL incompatible files included in Cacti project in include/treeview
feature: Added native jquery, jqueryui, and jstree
feature: Added new Tree navigation
feature: Added Columns to Tree (Preview only)
feature: Added new graph zoom to tree view and preview offering a "quick" (default) and an "advanced" mode

[Imperial]

A colleague who works daily with Google Chrome reported me the same problem since 2-3 Weeks, the Page load lags, aborts or required 15-20 seconds until chrome responds, this applies only in tree mode, the preview mode works fine, same result on my machine (but i work with Firefox), 2 other work places and on my Galaxy Note 3 wit Chrome, Firefox works fine!

OS: Windows 7 x64 SP1 & Windows 8.1 x64
Chrome: 41.0.2272.101 - 15-20 Seconds on Tree, lags, script aborts, ok in Preview Mode!
Firefox: 36.0.4 - ok
IE: 11.0.9600.17691 - ok

Note 3 Galaxy OS: Android 4.4.2
Chrome: 41.0.2272.96 - lag and script timeout on Tree Mode, ok in Preview Mode
Firefox: 36.0.4 - ok!

Server: Centos x64 16Gb Ram 2x Intel Xeon Octacore CPU
Cacti: 0.8.8b
Devices: 3800+
Graphs: ca. 34.000 (many of them are in the tree)