Closed Bug 1001593 Opened 11 years ago Closed 11 years ago

AnimationBenchmark/svg perf regression in Firefox 30

Categories

(Core :: SVG, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox28 --- unaffected
firefox29 --- unaffected
firefox30 --- affected
firefox31 --- verified
firefox32 --- verified
firefox33 --- verified

People

(Reporter: cpeterson, Unassigned)

References

()

Details

(Keywords: perf, regression, reproducible)

The following SVG benchmark is 2x slower in Firefox than Chrome and 6x slower in Firefox 30 than Firefox 29: http://themaninblue.com/experiment/AnimationBenchmark/svg/ * Chrome 34: 40–50 fps * Firefox 28: 30 fps * Firefox 29: 30 fps * Firefox 30: 5 fps * Firefox 31: 5 fps I bisected the regression to this pushlog: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=0085a162499f&tochange=8ed8185b72c4
jgilbert: could this regression be related to WEBGL_color_buffer_float bug 843666 or its backout in the regression range? I am testing on OS X.
Flags: needinfo?(jgilbert)
On Linux, mozregression gives me this range (which is a superset of cpeterson's range in comment 0, so cpeterson's range is more useful): https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=0085a162499f&tochange=ad3b57404218 I get 70-100 FPS pre-regression, and 1-5 FPS post-regression.
OS: Mac OS X → All
Hardware: x86 → All
Version: unspecified → Trunk
See Also: → 1001845
(FYI, For Windows7, I filed Bug 1001845, because the regression range is different from this)
I do not think this regression is related to a WebGL extension.
Flags: needinfo?(jgilbert)
I think this was fixed in Beta31. :cpeterson Could you try it in latest Beta31.0b5?
Flags: needinfo?(cpeterson)
I verified that the regression in Firefox 30 has been fixed in Beta 31, Aurora 32, and Nightly 33. Note that Chrome is still 2–3x faster (~80 fps) than Beta 31 with the fix (~30 fps).
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(cpeterson)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.