[Webkit-unassigned] [Bug 100872] r132913 caused a bunch of performance regressions and progressions

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=100872





--- Comment #4 from Ojan Vafai <ojan at chromium.org>  2012-10-31 12:45:30 PST ---
(In reply to comment #3)
> I think it makes sense to keep the patch in.  Mostly it's important to be aware of these issues and to make sure we're making the right trade-offs here.

Is a 33% regression on getElementById OK? In general, we have this policy of not leaving regressions in because it's hard to see when (if!) the regression gets fixed due to other patches going in that affect the performance.

Can we understand why this test case regressed so much? Not sure what having this patch on the Canary helps with in terms of addressing this benchmark.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.