Updates:
Cc: [email protected]
Labels: -Area-Misc Area-BrowserUI Pri-3
Comment #2 on issue 19671 by [email protected]: high cpu usage while
waiting server response
http://code.google.com/p/chromium/issues/detail?id=19671
I was not able to repro this effect. The highest steady state I was able
to get
chrome up to (just the browser process) was 30% of so. I had to get like
12 tabs or
so open to do that. Of course, I have a much beefier system than you, so I
dunno.
In any case, I'm not seeing a linear growth in cpu usage corresponding to
the number
of tabs open, if that's what you're implying.
That said, the most likely cause of whatever effect you're seeing is the
tabstrip
rendering. When you are navigating to a non-responsive url, you will get a
loading
animation for that tab. That loading animation will force frequent paints
of the
tab.
Indeed, when I start up my chromium _debug_ build and profile it, I note
that when I
open up 12 non-responsive tabs (i'm using 1.2.3.4, 2.3.4.5, ...), rendering
the
tabstrip accounts for roughly 50% of the chrome browser process's cpu
usage. My
numbers are somewhat suspect since it's a debug build, but whatever.
Anyhow, we haven't even begun to start optimizing chromium on Linux, so
it's not
surprising if it's slow in places. I've cc'd jhawkins in case he wants to
take a
look at tabstrip rendering performance, but I personally consider this low
priority.
Let me know if this is having a significant user visible impact on your
system.
Attachments:
cpuprofile.pdf 14.1 KB
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
