Closed
Bug 1123260
Opened 9 years ago
Closed 9 years ago
19% regression on octane-splay on January 16th, 2015
Categories
(Core :: JavaScript: GC, defect)
Core
JavaScript: GC
Tracking
()
RESOLVED
FIXED
People
(Reporter: h4writer, Unassigned)
References
Details
There is a 19% regression on octane-splay on x86 and x64 MacOSX shell slaves. http://arewefastyet.com/#machine=28&view=single&suite=octane&subtest=Splay&start=1421422389&end=1421624846 Combing the x86 and x64 regression ranges I get: http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=3d0dd2ae7e6c&tochange=cafc08288982
|
Reporter | |
Comment 1•9 years ago
|
||
So putting NI on terrence, since the regression range shows only patches from him.
Flags: needinfo?(terrence)
|
||
Comment 2•9 years ago
|
||
Thanks, Hannes! Splay does a ton more scanning of live objects than our other benchmarks, so I'm fairly certain that this is the extra budget check I added in bug 1111361. I'll try backing out that push and we can see what happens to splay.
Blocks: 1111361
Flags: needinfo?(terrence)
|
|
||
Comment 3•9 years ago
|
||
Nope, looks like I'm wrong: the backout is on awfy and the performance did not change. Cycling to 1119537.
|
|
Reporter | |
Comment 5•9 years ago
|
||
Thanks a lot. Confirmed fixed on awfy by the backout http://hg.mozilla.org/integration/mozilla-inbound/rev/aa05cd133a76
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•