Summary: | [GEN7] 10-20% drop in SynMark terrain tests perf, 4% drop in Manhattan 3.0 perf | ||
---|---|---|---|
Product: | Mesa | Reporter: | Eero Tamminen <eero.t.tamminen> |
Component: | Drivers/DRI/i965 | Assignee: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Status: | RESOLVED MOVED | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Severity: | normal | ||
Priority: | medium | ||
Version: | git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Eero Tamminen
2017-10-05 13:34:33 UTC
I don't have a Haswell GT2, but I tried to reproduce this on a Haswell GT3e. I tried both OglTerrainFlyTess and Gl41TerrainFlyInst on both commits, and the framerates were basically identical. So, I guess I cannot reproduce this. I can reproduce earlier good results, so the drop wasn't due to setup change on our HSW. During past ~3 months, there haven't been significant changes in terrain tests results before this on HSW GT2 (I don't have data for GT3e). So, kernel and X versions shouldn't matter that much (only change was modesetting dropping perf on BYT). Our Mesa test setup is currently using kernel 4.13 and X server from same time frame (mid September), with rest being Ubuntu 16.04. Maybe the issue requires GPU to be slower than yours compared to the CPU, to be visible? Our HSW is i7-4790, 1200Mhz GT2. If you don't have anything similar at your side, one option would be to try disabling one slice / eMMC or just lowering GPU max speed enough to make the tests fully GPU bound. During the same commit range there's also clear 15% drop in SynMark PSPom performance on BYT (with 1-channel memory). On HSW GT2, PSPom drop is 2%. Because GfxBench drops happen also with offscreen versions, I don't think it's required that Mesa would be used by the whole system (by X modesetting driver) like in our system. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1636. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.