#MICROSOFT EDGE VS CHROME QUORA WINDOWS 10#
Let me remind you, Windows 10 official spec requires just 1Ghz CPU with 1-2 GB RAM.
#MICROSOFT EDGE VS CHROME QUORA PC#
Chromium in sharp contrast has auto Tabs Discarding feature, which can be further enhanced with a choice of extensions, and makes possible to run Chrome on an older and slower PC and devices with numerous tabs open without any user effort.
Opening Edge Classic with a few heavy tabs takes out almost all available memory on an older PC with 4GB RAM, and then it crashes. If Edge Chromium is using CPU resources in static state, but Chrome is not, then Edge Chromium has an issue that is not present in Chrome, and that should be reported as a I want to help ensure that new Edge uses resources as sparingly as Edge (Classic)."Īre you for real? What in your view prompted the devs to move to Chromium engine then? Did you look at browser usage statistics lately? :) I don't know whether this pattern is related to the issue reported by Marco Mollace with respect to Brave or not, and I am not in a position to compare CPU use between Edge Chromium and Chrome, which would seem to me to be a more definitive and useful test.Īll I can suggest is that you run similar comparison tests between Edge Chromium and Chrome, and see if the results are similar or dissimilar. The screenshots from that time suggest that the CPU use pattern is not new with the most recent builds. I saw similar results in snapshot form (that is, Edge Chromium using 1-1.2% of CPU at rest, Edge (Classic) at 0%). At the time I was using an earlier Dev build (I don't recall which, but I think that it was the first Dev release).
This snapshot from the Dell XPS 8920 illustrates what I observed:Ī caveat: I checked several similar Task Manager screenshots (comparing Edge (Classic) and Edge Chromium, but not Firefox) that I used in a discussion related to Chromium-based process handling. In each case, over a period of 15 +/- minutes of watching Task Manager, an identical pattern appeared that was both persistent on each computer and consistent between the computers: Edge Chromium used 1-1.5% of CPU resources when in the static state described, but neither Edge (Classic) nor Firefox Quantum used CPU resources in the static state described. I am using the most recent Dev build (76.0.159.0).Īfter the browsers were opened an had a minute or two to settle down to static state, I opened Task Manager on each of the three computers and observed CPU use of the three browsers on each computer. I run Windows without visual effects (transparencies, shadows and so on) and I run all three browsers in native state, so no extensions or add-ons are running that could complicate results. Important is, such bugs should be urgently fixed to encourage users continue testing the browser, rather the masked as unrelated generic "known issue" that can not be fixed at did some comparison testing on CPU use this morning, opening instances of Edge (Classic), Edge Chromium and Firefox Quantum, each with 6 Bing tabs open, all in static state, on each of three Windows (a Dell XPS 8920, Intel i7, 16gb RAM, AMD Radeon 580 graphics a Dell Latitude 7280, Intel i5, 8gb RAM, Intel 620 graphics and a Dell Inspiron 3185, AMD a9420e, 4gb RAM, Radeon R5 graphics). Its on average 10 to 20 times higher for Edge, clearly pointing on a bug, which is not surprising for alpha builds we are offered to test. Compare 2 screenshots below: one is Edge with one tab open and no extensions installed using 20% of CPU and GPU resources, and another is Chrome with one tab open and multiple extensions running using 1% of PC CPU and GPU resources. I have to stop testing Edge Preview, and go back to using stable Chrome (despite both are based on multiprocess Chromium), because Edge now uses MUCH more system resources due to namely this bug or lack of optimization. It may also be a "known issue" to Edge developers, but your comment masks it for users thus making appear less urgent to fix, when in fact the opposite is true.
This brings us to second issue, namely very high CPU and GPU load in current Edge Preview builds due to bug or lack of optimization. So your comment does NOT match the topic of this thread. In that regard both Edge Preview and Brave are similar, as both are based on Chromium and use a separate process per tab. One issue as you mentioned is browsers using a separate process per tab may consume more system resources than browsers using one common process for all open tabs.
0 kommentar(er)
