16% regression on shumway-splay on February 26th, 2015

RESOLVED INCOMPLETE

Status

defect
RESOLVED INCOMPLETE
4 years ago
3 years ago

People

(Reporter: h4writer, Assigned: till)

Tracking

({perf})

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
AreWeFastYet is showing a regression on Shumway splay:
http://arewefastyet.com/#machine=28&view=single&suite=shumway&subtest=splay&start=1424184636&end=1424928007

Mozilla: 16.4% regression
Chrome: 30% regression

Local testing showed this is a shumway issue. Bisecting points to (as first bad revision):
https://github.com/mozilla/shumway/commit/02e1c500298fe375ea18bdcbd0640bd5a5ddfe27
(Reporter)

Updated

4 years ago
Flags: needinfo?(till)
(Assignee)

Comment 1

4 years ago
Some more bisecting shows this to be caused by https://github.com/mozilla/shumway/commit/18e7617bf4e55c96b496116fc5ed41ae363ef7eb. Which is annoying, because that'll be hard to debug and probably even harder to fix :(
Flags: needinfo?(till)
(Assignee)

Comment 2

4 years ago
This is caused by a change I made to how our builtins are initialized. Will see how to fix.
Assignee: nobody → till
Till says this not really actionable. He wants to test with new compiler.
Blocks: shumway-1.0
Blocks: shumway-m5
No longer blocks: shumway-1.0
Keywords: perf
Product: Firefox → Firefox Graveyard
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.