That image was inserted there. Try #2.
bp
<part15sbs{at}gmail{dot}com>
On 3/10/2015 5:47 PM, Bill Prince wrote:
I tried running it on my old Windows XP machine. Same problem.
I did run the developer's profile tool, and it is spending a lot of
time (most of it in fact) in ftiens4.js. See below. Something about
painting the tree.
bp
<part15sbs{at}gmail{dot}com>
chromegraphCPUprofile.PNG
On 3/7/2015 6:01 PM, George Skorup (Cyber Broadcasting) wrote:
I want to say that's the exact same problem I was seeing the other
day. Chrome kept freaking out saying connection lost or something
like that, and it was only happening when going through Cacti pages.
Closed/reopen Chrome, reboot my PC, and then... a couple hours later,
it just went away. I assume the Google changed some crap and messed
it up like they usually do. I don't know how to force gupdate to run.
So I just did something else for a while because it was pissing me
off. I hate it, it's a memory hog and uses lots of CPU cycles. But it
lets me have all of my bookmarks and passwords sync'd across all
devices and PCs.
My version is the same as yours currently. This was a couple days ago
too. So I'm not sure that has anything to do with it. Have you tried
Chrome on another PC?
But Thursday night, I also migrated my Cacti over to a new machine.
The old one started running dogshit slow a couple months ago. I found
out that one of the CPUs sorta half failed. One of the logical
processors, aka hyper-threads, will not start. The kernel says "CPU
not responding - cannot use it" at boot. And I think that socket is
also tied to the half of the PCI bus that runs the RAID controller
slot. The thing is well over 10 years old, so it got some good life.
The new machine is dual socket with 6-core Hyper-threaded Xeons each
and lots more RAM. It's.. fast. I get a 30 graph page in under 2
seconds now. It would take like 2 minutes to get a net-flow report,
now it's about 5 seconds.
On 3/7/2015 2:23 PM, Bill Prince wrote:
For about the last week, I've been seeing extremely _S_L_O_W_ graph
rendering in cacti, but only when I use a chrome browser. Both
firefox and IE at least 10X faster. An average subscriber with 8
graphs takes about 1 second if the browser is firefox or IE, but
chrome takes something like 20 seconds; sometimes even longer (one
time ~~ 45 seconds).
I thought maybe it was an extension or something, so I turned off
extensions and stripped it down to next to nothing. No help. So I
am guessing this is some issue with the way that rrdtool renders the
graph(s) and the way that chrome interprets it or something.
When I do the operation in either firefox or IE, the CPU utilization
goes up for a brief little blip. When rendering in chrome, CPU
utilization goes up to ~~ 50-60% and stays there until the page is
rendered; 20, 30, sometimes 40 seconds. I also get timeout notices
from chrome. I tell it to "wait", and eventually the page is
rendered....
My setup:
Windows 8.1 x64 (whatever the latest update is)
chrome Version 41.0.2272.76 m (64-bit)
firefox Version 36.0.1
--
bp
<part15sbs{at}gmail{dot}com>
