Bug 1339557 (Speedometer_V2)

[Meta] Quantum Release Criteria: Figure out why we are so slow on Speedometer v2

NEW
Unassigned

Status

()

Core
JavaScript Engine
4 months ago
5 hours ago

People

(Reporter: Ehsan, Unassigned)

Tracking

(Depends on: 33 bugs, Blocks: 1 bug, {meta})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [qf:investigate][qf:meta], URL)

See <https://twitter.com/bz_moz/status/831585613258379265>

We have looked at this before a bit, see bug 1245279 and bug 1022988.  We need to profile again and find out why we are so slow.  This is important since this test executes a bunch of popular frameworks.

Andrew, can we find an owner for this please?
Flags: needinfo?(overholt)
Let me work on it.
Depends on: 1339593
I spent a bit of time looking at some random profiles from a long Speedometer run and all I can see is JS.  Perhaps someone on the JS team would be a better candidate.
Component: DOM → JavaScript Engine
Flags: needinfo?(nihsanullah)

Updated

4 months ago
Depends on: 1245279

Comment 3

4 months ago
Marked improvement overnight after fix via bug: 1339535

My fiber today is shocking for some reason, but still seeing a ~35% speed improvement. Testing in another location in around an hour.

Arch Linux rolling release. Nightly 2017-02-28 vs 2017-02-27. Dell Latitude E4300 16Gb RAM.
Flags: needinfo?(nihsanullah)
Whiteboard: [qf:investigate][qf:p1]
Flags: needinfo?(overholt)

Updated

3 months ago
Depends on: 1346723

Updated

3 months ago
Depends on: 1347525

Comment 4

3 months ago
Despite improvements to Nightly, which I've experienced on my laptop since Feb 27, testing is now shockingly slow on a Galaxy Tab A (9.7) running Fx55. Speedometer test been running for 45 mins and not yet half way :(

Updated

3 months ago
Whiteboard: [qf:investigate][qf:p1] → [qf:investigate][qf:meta]

Updated

a month ago
Depends on: 1366250
Alias: Speedometer_V2
Keywords: meta
Summary: Figure out why we are so slow on Speedometer → [Meta] Figure out why we are so slow on Speedometer v2
Depends on: 1356315
Depends on: 1364854
Depends on: 1346546
Depends on: 1364908
Depends on: 1349924
Depends on: 900784
Depends on: 1022714
Depends on: 1022988
Depends on: 1245294
Depends on: 1355472
Depends on: 1363438
Can we put a link to the v2 speedometer in this bug?  Not sure where it lives.
Depends on: 1357862
I added it to the URL field of this bug.
Depends on: 1363829

Updated

a month ago
Blocks: 1366777

Updated

a month ago
No longer blocks: 1366777
Depends on: 1366803
Depends on: 903519
Depends on: 1367458
Depends on: 1349255
Depends on: 1338802

Updated

a month ago
Alias: Speedometer_V2 → QRC_Speedometer_V2
Summary: [Meta] Figure out why we are so slow on Speedometer v2 → [Meta] Quantum Release Criteria: Figure out why we are so slow on Speedometer v2
Depends on: 1351769
Depends on: 1365361
Depends on: 1366263
Depends on: 1366375
Depends on: 1366377

Updated

29 days ago
Alias: QRC_Speedometer_V2 → Speedometer_V2
Depends on: 1364805
Blocks: 1325169
No longer blocks: 1337841

Comment 7

27 days ago
According to bug 1347525 slow InnerHTML is the main reason for Firefox's slowness in Speedometer. This was resolved, but Speedometer is still at best only half as fast as in Chrome for me. 

With an i7 6700k I get 199 runs/minute in Chrome, 98 runs/minute in Firefox. This scales down with CPU power, on an i5 6200U I get 42 runs/minute with Firefox, 88 with Chrome.

How relevant is Speedometer for Gecko, anyway? V8 describes it as a great tool for measuring real world performance, however in bug 1347525 comment #3 seems to suggest otherwise.
(In reply to TMart from comment #7)
> According to bug 1347525 slow InnerHTML is the main reason for Firefox's
> slowness in Speedometer.

I never said that. In that bug I was talking about one of the subtests, but there are a lot of these and we knew fixing that bug would not magically fix everything.

> With an i7 6700k I get 199 runs/minute in Chrome, 98 runs/minute in Firefox.
> This scales down with CPU power, on an i5 6200U I get 42 runs/minute with
> Firefox, 88 with Chrome.

This might be better with Speedometer v2.

> How relevant is Speedometer for Gecko, anyway? V8 describes it as a great
> tool for measuring real world performance, however in bug 1347525 comment #3
> seems to suggest otherwise.

There are a bunch of silly things for sure. Overall it's not an unreasonable benchmark though and so far almost all performance issues we found/fixed will help real-world websites too.
Duplicate of this bug: 1022239

Updated

24 days ago
Depends on: 1369140
No longer depends on: 1363829

Updated

24 days ago
Depends on: 1364816
Depends on: 1369587
No longer depends on: 1369587

Updated

19 days ago
Blocks: 1370336

Updated

19 days ago
No longer blocks: 1325169
Depends on: 1371097
Depends on: 1372794
Depends on: 1372974
Depends on: 1373063
Depends on: 1373672
Depends on: 1373723
Depends on: 1374033

Updated

6 days ago
Depends on: 1374112

Updated

6 days ago
Depends on: 1374119
Depends on: 1374416
Depends on: 1373079
Depends on: 1374892
Depends on: 1375568

Comment 10

2 days ago
The machine that runs speedometer got this morning a change that will make the score of speedometer improve (bug 1373396).

I don't know how it will affect the score of Chrome but we will know later today. AWFY is currently running:
https://arewefastyet.com/#machine=36&view=breakdown&suite=speedometer-misc

Also note that we currently run non-PGO builds for speedometer which could mean that our score could even be a bit higher.
Depends on: 1375573
Depends on: 1375599
Depends on: 1375619
Depends on: 1375331
Depends on: 1375701
Depends on: 1375741
You need to log in before you can comment on or make changes to this bug.