[Bug 107410] [SKL] Up to 20% performance regression in GpuTest Triangle, due to 2x higher CPU power usage

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Jul 30 14:13:30 UTC 2018


https://bugs.freedesktop.org/show_bug.cgi?id=107410

--- Comment #10 from Eero Tamminen <eero.t.tamminen at intel.com> ---
Heaven wasn't impacted in my tests either.   Only simpler tests were.


(In reply to Eero Tamminen from comment #0)
> There were following 3D benchmark performance regressions on SKL GT4e:
> - 20% GpuTest Triangle (windowed & composited, half screen size)

./GpuTest /test=triangle /width=1366 /height=768 /msaa=1 /no_scorebox
/benchmark /benchmark_duration_ms=35000

(Composited with Unity desktop compositor as it's windowed.)


> - 10% GpuTest Triangle (FullHD fullscreen i.e. slower)

./GpuTest /test=triangle /width=1920 /height=1080 /fullscreen /msaa=1
/no_scorebox /benchmark /benchmark_duration_ms=35000

Test does just a clear and draws single triangle covering half a window, so
this test is as trivial as glxgears.


GpuTest is the benchmark from here:
https://www.geeks3d.com/gputest/

(Score it reports is just the number of frames rendered.)



> - 1-6% SynMark Batch[2-4]

Batch0-7 are a series of tests where about 2M of triangles of are drawn.  In
Batch0 they're with a single draw call, in Batch1 they're split to two calls,
in Batch2 to 4 calls etc.  At or after Batch5 i.e. 2M of triangles being split
to 32 draw calls, tests start to become CPU bound.


> - 1-4% GfxBench Tessellation (onscreen only), GpuTest Julia32 (windowed), SynMark GSCloth & ShMapPcf (fullscreen)

GSCloth  does 72 draw calls per frame, Tessalation test 50, ShMapPcf 7, and
Julia32 does 2 of them.  Julia32 is fastest of these and GSCloth slowest
(GSCloth may be slightly CPU bound).

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180730/a0ed2ab9/attachment.html>


More information about the intel-gfx-bugs mailing list