Closed
Bug 712541
Opened 13 years ago
Closed 13 years ago
FF doesn't fully utilize 2+ cores
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 516518
People
(Reporter: rockachu2, Unassigned)
Details
Attachments
(1 file)
232.52 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:12.0a1) Gecko/20111220 Firefox/12.0a1
Build ID: 20111220112824
Steps to reproduce:
Ran the Kraken JS test:
http://krakenbenchmark.mozilla.org/
And looked at CPU usage
Actual results:
There was very little by cpu (<7% each), but FF was using 18% of the cpu total.
Expected results:
All cores to max out and the test to complete fast.
EDIT:
Now some of the cores are being used, but still, not all of them as it should be.
Comment 3•13 years ago
|
||
And did you test this with other browsers ?
I don't think that parallelization would work here.
since I can't edit the bug expected results,
thanks for pulling me up on that one. If full parallelization isn't possible here, then at least the UI should be paralleled to the main thread for this test. Running it basically freezes the UI until the test completes.
I tested in IE, and it shows the same problems: Low CPU usage and UI lag.
Opera Next (beta/dev?): Same, but less UI lag, probably because it is doing some other things (got a REALLY low score.)
Chrome Dev: Doesn't fully utilize cores, but there is NO UI lag. (I could move tabs around and open menus while the test was running)
Comment 5•13 years ago
|
||
Chrome is using one process per tab but you get other problems with that if you open many tabs (=many processes).
Using one process for each tab in Gecko is bug 516518
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•