<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - 3% perf drop in GfxBench Manhattan 3.0, 3.1 and CarChase test-cases" href="https://bugs.freedesktop.org/show_bug.cgi?id=111090#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - 3% perf drop in GfxBench Manhattan 3.0, 3.1 and CarChase test-cases" href="https://bugs.freedesktop.org/show_bug.cgi?id=111090">bug 111090</a> from <a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> Eero Tamminen</a> <pre>(In reply to Eero Tamminen from <a href="show_bug.cgi?id=111090#c14">comment #14</a>) > There were following perf changes on SKL GT2 & KBL GT3e: > * SynMark VSTangent improved by 10% > * GLB 2.7 Egypt improved by 1-2% > * GLB 2.7 T-Rex improved by < 1% > * SynMark ZBuffer decreased by 5% KBL GT3e and 3% on SKL GT2 (*) On BXT, ZBuffer perf had actually also increased (from what it was month ago, as I don't have closer "before" data), and on BDW GT2 there was no change in it (although other listed cases did improve also on BDW GT2). I.e. I think ZBuffer drop on SKL / KBL can be ignored. It's been only significant kernel perf change since this bug, besides the one around 22nd of June, with 5% improvement in SynMark Batch0, 1-4% in VS* and 4% perf drop in SynMark GSCloth & ShMapPcf on SKL GT2 (and marginal changes on other core devices).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>