Closed Bug 1088231 Opened 10 years ago Closed 10 years ago

3.3% Linux32 Dromaeo DOM regression on Inbound (v.36) Oct 22 from push 59be1e005220

Categories

(Core :: DOM: Core & HTML, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: jmaher, Unassigned)

References

Details

(Keywords: perf, regression, Whiteboard: [talos_regression])

None of the code I removed in bug 1019191 ran during dromaeo-dom.

How was the changeset in "here is the changeset" determined?  The tbpl view shows a number of js engine changes, right?
Also, the chart doesn't show an obvious regression over the entire highlighted range...
if you look at the tbpl view, you can click on the 'd' and see the value for dromaeo DOM.  we have a noticeable drop when we get to 59be1e005220.  Let me retrigger some to help highlight or disprove it:)
I would be somewhat, but not incredibly, surprised if removing dead code changes performance characteristics... ;)
the retriggers show a regression with this push (~900 before, ~880 after), but I see a win (~890) from this push (2 later):
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?changeset=d6d519cc677b

as this appears to be linux32 and the net regression is very small (if any at all now), I recommend closing this as wontfix.
Worksforme.  Especially since the changeset the win is from doesn't change any code used by dromaeo-dom either.  :(
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.