Browser and GPU process are much higher compared to Brave

sambul95  

tomscharbach:  "We've had a dozen threads requesting that Microsoft do what it can to reduce resource use in Edge Chromium by bundling processes ..."

sambul95:  "You might be interested to read this thread: Why are there multiple Chrome instances running even though I only have one window open? Its improving stability, security, and responsiveness."

I initially posted about Chromium's resource-hogging proclivities because I misunderstood the nature of Marco's initial post, which was about excessive CPU usage at rest. If I had understood his initial post, I would have gone right to testing, in order to identify, isolate and document the bug we've reported in this thread.

I'm well aware of the reasons that Chromium uses multiple processes instead of bundling, and if you read the numerous earlier threads in which the topic is mentioned, comments will point you back to 2008 technical documents in which the pros and cons were hotly debated in the early days of Chromium development for the Linux platform.

It seems to me that is a topic you should take to another thread, if you want to do so.

I agree with your observation (stated in your post above this latest edit): "This topic is dedicated to a very important bug." I agree with that, and with your advice to in a more recent thread to "stay focused". Let's not get sidetracked.

Aaron44126   Thanks, Aaron.  I was able to replicate your results on a Dell XPS 8920 (i7, 4 physical cores, 8 logical processors).   The Edge Chromium Task Manager showed 139.6% CPU use, while at the same moment, Windows Task Manager was showing 20.5% CPU use.   I think you've confirmed that the two measure/report CPU usage on differently, and your single/multi core explanation makes sense to me.

Aaron44126 

It well may be that one CPU core power in https://superuser.com/questions/162590/setting-permanent-process-cpu-core-affinities-in-windows or Chrome https://chromium.googlesource.com/chromium/src/+/master/docs/threading_and_tasks.md is enough per Chromium process to render most webpages. It looks like Browser Task Manager is designed to reflect that as you suggested earlier. :)

sambul95 I ran the SunSpider JavaScript benchmark and here you can see an Edge process using more than 100% CPU.  (At one point it spiked to over 200% but I missed grabbing a screen shot for that.)

tomscharbach 

"run with admin privileges"

You can start a new topic about Edge Chromium Roadmap, sure many folks will contribute. This topic is dedicated to a very important bug. Edge Chromium Program Manager was working for Google Chrome Security team just months ago, so you can address your concerns to the right guy if they are justified. :)

"We've had a dozen threads requesting that Microsoft do what it can to reduce resource use in Edge Chromium by bundling processes"

You might be interested to read this thread: https://superuser.com/questions/461552/why-are-there-multiple-chrome-instances-running-even-though-i-only-have-one-wind   Its improving https://docs.microsoft.com/en-us/windows/desktop/ProcThread/about-processes-and-threads, https://www.chromium.org/Home/chromium-security/site-isolation, and https://blog.chromium.org/2008/09/multi-process-architecture.html. While I agree OS developer company is better positioned to cut on browser resource usage, if its various teams interact properly. For that to happen, a top level MS exec must be keenly interested in Edge success, given current minuscule market share and revenue from it. Now it looks more like a prestige project, though they put 200 heads on it. Keep pushing on the right buttons. :) Or https://www.ghacks.net/2015/02/08/save-memory-in-chrome-by-using-one-process-per-site/ on your own.

sambul95  "My main concern is, Edge Preview devs have an approved roadmap, which directs them to concentrate on full set feature transfer, and moving from Chrome to MS services. Which means, performance optimization issues may be very last ones on their mind right now."

Your comment suggests that you have access to the Edge team's official roadmap in some form. I understand that you may have to keep the details close to your chest, but could you comment about whether or not removing the Edge Chromium's ability to run with administrator privileges is on the roadmap?

I don't run Chrome on my computers, in part, because I have five or six concerns about Chrome's security.  The ability to run with administrator privileges is high on that list of security deficiencies, because it isn't all that hard to bypass/escape a sandbox.

EbonJaeger 

Following the same logic, can you give some alternative links for Chromium Task Manager? I'm merely asking for sources, not sure how it measures the load. :)

It's pretty common knowledge that the CPU usage percent in Windows Task Manager is normalized across the CPU's logical cores. A quick search would have told you. :)

For example:

https://www.quora.com/What-is-the-meaning-of-CPU-usage-in-a-windows-task-manager

https://superuser.com/questions/994191/what-does-cpu-column-means-on-process-tab-on-task-manager

sambul95 

tomscharbach:  "I was wondering why the metrics were so different. Now I know. "

sambul95: "I'd ask for some references before saying that."

I accepted Aaron44126's explanation (different ways of dealing with cores) because it made sense.

I know one half of the equation:  Windows 10 Task Manager tracks usage across all logical processors (typically two per physical core) and measures % of CPU cumulatively across the logical processors:

I don't use Google Chrome on Windows or Chromium on Linux, so I'm not familiar with the Chromium-based task manager.  Accordingly, I don't know anything about the other half of the equation -- how the Chromium-based browser Task Manager tracks usages across physical/logical cores/processors.  

You seem to have a high level of technical expertise, and you seem to be challenging Aaron44126's explanation, so let me ask you this:  To what do you attribute the differences in CPU usage measurement between Windows 10's Task Manager and Edge Chromium's Task Manager when measuring CPU usage under identical conditions?  I'm curious to know why you think that this is happening, if you don't accept Aaron44126's explanation.  Clearly the two task managers are measuring something differently.

sambul95

I too stopped using Chromium Edge too due to performance problem. I switched back to Google Chrome and was surprised that my laptop got quiet again :-(. Very sad. I hope MS will fix this performance issue very soon.

I reported this issue via feedback and attached screenshot with task manager showing CPU and GPU consumption in idle state when only start page is open.

Aaron44126 

I'm sorry to repeat my basic question: where did you get this info from? :) Can you support it by any web links or screenshots?

sambul95 I stated nothing of the sort.  I just stated that what the "CPU %" shown in Task Manager means is different between the two... task managers.  To compare the two you have to multiply or divide by the number of logical cores in your system.  If one process within Edge process uses more than one CPU core it will register higher than 100% in Edge task manager

tomscharbach 

"What processor are you guys using to get CPU use results in the 20-30% range, if CPU power is the driver on this issue?"

It was already answered in this thread. Look no further than Win 10 official specifications: 1Ghz CPU, 1-2 GB RAM. That MUST be Edge devs target as per MS Policies and common sense, since Edge is internal Windows app. Don't forget, near same code is likely used not only on PCs, but Windows Mobile devices of various gens, Tablets and very basic and cheap Atom and such student notebooks sold in huge quantities.

"I was wondering why the metrics were so different. Now I know. "

I'd ask for some references before saying that.

Aaron44126 

Are you stating that Edge Chromium uses only ONE core of ANY CPU? Where did you get it from? Also, I don't need to look at any Task Manager - when my laptop fans are sounding like turbines all the time I know Edge is idling, now uninstalled. :)

My main concern is, Edge Preview devs have an approved roadmap, which directs them to concentrate on full set feature transfer, and moving from Chrome to MS services. Which means, performance optimization issues may be very last ones on their mind right now. So no such bugs might be fixed in forceable future, thus cutting off current enthusiastic but fast shrinking testers pull. There always be some hardcore folks, knowing little about tech, but asking to add this or that classic button or check box thinking Edge team "forget" it, so targeted "web noise level" will be maintained.

Aaron44126 "Keep in mind: It appears that there is a discrepancy between the number reported between Windows Task Manager and the browser's Task Manager.  Windows Task Manager reports the CPU use where 100% would mean that all logical CPU cores are fully loaded.  (i.e. In a system with 8 logical cores, 100% would mean that all 8 are under a full load whereas a single-core load would be 12.5%.)  The browser task manager reports 100% for one core worth of full load, so an 8-core load would be 800%.  Something to keep in mind when making comparisons."

Thanks, Aaron.  I was wondering why the metrics were so different. Now I know.  

Keep in mind: It appears that there is a discrepancy between the number reported between Windows Task Manager and the browser's Task Manager.  Windows Task Manager reports the CPU use where 100% would mean that all logical CPU cores are fully loaded.  (i.e. In a system with 8 logical cores, 100% would mean that all 8 are under a full load whereas a single-core load would be 12.5%.)  The browser task manager reports 100% for one core worth of full load, so an 8-core load would be 800%.  Something to keep in mind when making comparisons.

Marco Mollace ""Edge Chromium isn't using more than 6-7% at rest." CVD, there's an issue. It should stay around 0%"

Absolutely.  That's what I've been documenting throughout this thread, as carefully as possible, using Windows Task Manager, comparing browsers.  Edge Chromium uses CPU resources at rest; other browsers (Edge (Classic), Firefox, Chrome) don't.  Something is not right with Edge Chromium, or it would not be using CPU at rest.

On a related topic, I did a comparison using the in-built Browser Task Manager in Chrome and Edge Chromium.  The difference in CPU use shows up there, as well, and the numbers are closer to the results you and others have been reporting.

This is the side-by-side results for Edge Chromium (left) and Google Chrome (right) on the Dell Inspiron 3185: