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?
Let me work on it.
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.
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.
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 :(
Whiteboard: [qf:investigate][qf:p1] → [qf:investigate][qf:meta]
Summary: Figure out why we are so slow on Speedometer → [Meta] Figure out why we are so slow on Speedometer v2
Can we put a link to the v2 speedometer in this bug? Not sure where it lives.
I added it to the URL field of this bug.
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
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.
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.
I see PollWrapper() in profiles, has anyone tried to understand why? Like is it the test designed to short break between runs, or is it firefox waiting on something?
(In reply to Ting-Yu Chou [:ting] from comment #11) > I see PollWrapper() in profiles, has anyone tried to understand why? Like is > it the test designed to short break between runs, or is it firefox waiting > on something? The test schedules a lot of asychronous work, such as loading web pages from the network, but it doesn't measure the entire time that it runs. See this function for what the benchmark really measures: https://github.com/WebKit/webkit/blob/057552ca85b3efd9c97d13a0f044abd0daba7526/PerformanceTests/Speedometer/resources/benchmark-runner.js#L121
The previous Speedtest v2 URL showed a "Not Found" page. I have been told that this is the correct URL to use (despite a page title of "Speedtest 1.0", which I'm told is incorrect).
You need to log in before you can comment on or make changes to this bug.