Thanks for the report.

Could you elaborate what sites your browser is opening, and which tab
(or browser process?) is consuming CPU.

10% or 20% are somewhat vague target, and such CPU could be reasonable
if the page is doing something useful in the background.

If you could pinpoint something specific is consuming CPU more than expected,
we'd appreciate it and be happy to work on fixing.

Otherwise, in a broader sense we are working on resource management
optimization and will close this as wontfix without specific issue.

CPU usage seems to spike when google drive is open, sometimes up to 40 percent. It also uses quite a bit of RAM. 

Issue is still present. Please confirm and fix. Google Drive causes CPU usage spikes. I have isolated it to the drive being open causing a memory and CPU cycle leak

Unable to reproduce this issue on Windows-10 using chrome latest Beta M57 #57.0.2987.54 & #57.0.2987.21. By opening few documents,sheets and presentations from google drive Observing not more than 5% of CPU usage in chrome task manager.

Reporter@ Could you please recheck this issue by upgrading to chrome latest M57 #57.0.2987.54 by creating a new profile under chrome://settings with no third party apps or extensions in your browser.

Thanks!

Thank you for providing more feedback. Adding requester "kochi@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Rechecked the issue on chrome beta version 57.0.2987.74 On Windows 10, MAc 10.12.3, ubuntu 14.04. No spike is observed in task manager when using Google drive.

@ tunca007: Request you to please upgrade chrome to the latest available BETA and try again. Please update us with your observations.

Thanks.!

I am on the latest beta and am STILL seeing the CPU usage spike. It is a big spike of roughly 40-50 percent. It lasts for about half of a minute to a minute before CPU usage drops again. 

I urge you and the other devs to continue to work on resource management optimization for Google Chrome. Keep in mind that I'm running Windows 10 insider preview build 15042. 

Thanks for more info.

I tried opening Google Drive on a tab in M56 on Windows 10 (anniversary update,
not insider preview), and observed CPU usage and memory consumption.

For CPU, for ~10seconds after reloading the CPU spiked but settled to almost 0%
after that.  The number vary wildly, but like ~20% or so.

For memory, at the maximum I observed it ate 780MB but after some time (after GC??)
the usage went down to ~300MB.

Both are observed on Chrome's task manager, but those numbers can vary wildly
depending on your free memory, CPU power (I used 16GB mem, i7-6700K 4 core
8 threads here) and the usage of Google Drive (I have 1TB drive, 900+GB is
already used).

tunca007@, could you elaborate why you thought it is a resource management
optimization's fault and it could fix the situation?

Simply put, if there is an issue resulting in CPU and/or memory spikes, it means that Google Chrome needs to be further optimized to use less system resources. I am running an i5-6200U with 6 gigs of ram. I would work closely with Microsoft to optimize google chrome for insider preview builds and the new features that they are introducing. Focus on improving the user experience for people using lower powered systems, especially laptops (battery life considerations). 

Yeah, there are always opportunities for Chrome to optimize something.

I'm wondering if this is just Google Drive web app is behaving badly and
wasting lots of memory and CPU, or Chrome is doing poor job doing the same
job with less memory/CPU. Maybe both. Any web app can behave badly, and
Google Drive is not an exception.  So I'd think it's too early to conclude
Chrome has room to run Google Drive app better.

What we (Chrome developers in general, not only myself) can do is to identify
the problems, prioritize them, and work on fix them.  At this point the problem
is still vague and needs more drill down what is going wrong to make this
actionable.

If you are willing to, Chrome has tracing facility (the document can be found
at http://dev.chromium.org/developers/how-tos/trace-event-profiling-tool/recording-tracing-runs )
and you can run it yourself to see what is taking CPU resources.

Even if you can just run tracing to record logs, and post the log here
would help us finding what went wrong.

Please find attached the trace. 

Both Chrome and Google Drive can and should be improved. The Google Drive web app probably is behaving badly. 

Deleted: trace_Tue_Feb_28_2017_8.30.48_AM.json.zip 12.1 MB

trace_Tue_Feb_28_2017_8.30.48_AM.json.zip 12.1 MB Download

Thanks for your quick turnaround!

Could you pinpoint where in your trace data that is "CPU and/or memory spikes"
caused by Google Drive, or where you find Google Drive app is behaving badly?

Also, do you have any reasoning why you consider Chrome's behavior is
specifically bad?
(e.g. compared to Edge or Firefox's behavior, Chrome is taking XX% of CPU,
YYMB of more memory etc.) ?


Though I have been here for facilitating, I'm not the person to look into the
performance data in detail - someone else should take a stab at the data,
but before then please clarify where we should focus.

I started the trace as I opened google drive so when it says "active" is when the cpu is spiking. When it is idle, cpu usage should be fairly normal. That's where to focus. 

Chrome is a LOT better than it used to be, but it's still more resource intensive then edge and firefox. It uses quite a bit more memory (hundreds of megabytes) and a few percent more cpu. Firefox and Edge are more battery efficient which is the primary thing. Chrome drains the battery faster. 

Please get other devs to look into the performance data. Chrome has great features and is very fast; now work needs to be done to lower resource usage and negative impact on battery. 

Thanks for the reply and your input.

If I understand you correctly, this seems like a research project, to reduce
power consumption, CPU usage and memory usage.  They are exactly some of
Chrome's goals, but its too broad to discuss the problem here.

This issue tracker is usually for a specific, identifiable, and preferably
reproducible bugs, and is not suited to pursue for general goals, like
"use less power", "reduce CPU", "use less memory", or all.

At first I assumed this is something that Chrome is misbehaving specifically
on Google Drive web app, by a very specific bug, which is reproducible.
I and other tester tried to reproduce, but haven't seen anything suspicious.
So I assumed the running environment (e.g. memory is so tight, CPU is very
under powered) could be a potential issue, but from comment #11 this is not
the case.

Chrome sometimes uses intentionally more memory to achieve speed (as always
there are trade offs) than other browsers, when free memory is available.
So using more memory isn't always a bug.

As a whole Chrome project, there is already running project to reduce
memory, optimize CPU utilization, reduce battery drain, and so on, and
we are aware of these issues already.

If you are interested in getting more involved to solve the performance or
resource consumption issue in general, using a Google Drive app as a start
point, and I'll support anything you need (e.g. how to join discussion forum).

But from the discussion so far, I'd like to close this issue as nothing is
immediately actionable, sorry about that.

Additional note: please don't feel bad, your statement about the issues are
all real and nothing is wrong, and I agree Chrome should address them.

We have projects resolving these issues and cannot prioritize specifically
for Google Drive in a certain environment which may (or may not?) involve
many factors (e.g. maybe we can cut the memory usage by half, but it can
make it 2x slower - there are always trade-offs among various factors,
balancing them are hard problem).