There's up to 10% performance drop on *all* GEN8+ platforms, exactly same as in bug 107510.
On SKL GT2, the regressions are following:
- 10% GfxBench Tessellation (onscreen & offscreen)
- 5% SynMark2 GSCloth
- 2-3% GpuTest Julia FP64
- 1-2% Unigine Heaven (high quality with tessellation, no AA)
- 1% GfxBench ALU2 (onscreen & offscreen), SynMark PSPom
On other GEN8+ platforms the regressing cases are the same, but percentages differ somewhat. Performance didn't improve in any test.
- Mesa from git
- drm-tip kernel and X server git versions within couple of months
- Modifier support enabled (shouldn't matter as offscreen versions also regress)
Regressions happen between following Mesa git versions:
* 855af9a5a2: 2018-08-23 16:00:28 "travis: use python3 for the autoconf builds"
* 7f745c19c1: 2018-08-24 16:35:24 "docs: Update calendar, news, relnotes for 18.1.7"
(Jason's array splitting commits seems most likely thing affecting these.)
*** Bug 107743 has been marked as a duplicate of this bug. ***
8d8222461f9d7f497d657c2c0eff70820986429b is the first bad commit
Author: Jason Ekstrand <firstname.lastname@example.org>
Date: Mon Jul 23 22:20:41 2018 -0700
intel/nir: Enable nir_opt_find_array_copies
Fix to bug 107223 hid this regression from few of the high FPS onscreen tests, but otherwise performance of these hasn't changed in past few months.
Is somebody working on fixing this regression? (bug isn't assigned to anybody)
How sure are we of that bisect? None of the optimizations in that series affect gfxbench tessellation at all. I'll keep digging a bit.
the regression is pretty clear:
I did bisect manually on my skl. My recollection is that the delta was obvious at each iteration.
*** This bug has been marked as a duplicate of bug 107510 ***