Something in this range:
Appears to have caused a 10% PLT regression:
Notice the first spike when those revs were rolled into Chromium in Chromium@99936 and then the sustained rise after they were rolling in again in Chromium@100029.
I don't know whether this manifests on ports besides Chromium or on other test suites besides intl1.
i'll check our tests on Monday.
(In reply to comment #2)
> i'll check our tests on Monday.
I've made some bisecting steps.
94619 - bad
94588 - good
(In reply to comment #3)
> (In reply to comment #2)
> > i'll check our tests on Monday.
> I've made some bisecting steps.
> 94619 - bad
> 94588 - good
it is 94589
Author: firstname.lastname@example.org <email@example.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Date: Tue Sep 6 19:21:52 2011 +0000
[skia] never draw with GDI, so that all text can be gpu-accelerated
Reviewed by Kenneth Russell.
Would it make sense to roll out that patch while we investigate? We don't want this perf regression to hide other problems.
(Just so others don't spend too long looking, this patch is after the M15 branch point.)
What's the current status of this issue? What the patch rolled out? Was the performance regression fixed?
*** Bug 69239 has been marked as a duplicate of this bug. ***