Summary: | performance regression in Heroes of the Storm with Mesa 19.1.1 & Polaris | ||
---|---|---|---|
Product: | Mesa | Reporter: | tempel.julian |
Component: | Drivers/Vulkan/radeon | Assignee: | mesa-dev |
Status: | RESOLVED MOVED | QA Contact: | mesa-dev |
Severity: | normal | ||
Priority: | medium | ||
Version: | 19.1 | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
tempel.julian
2019-06-25 14:37:41 UTC
Can you try to revert 410759091173fa61436ba46baeb20a79d5767849 ? Btw, 158 vs 168 is really a small diff. It's an additional loss on top of DXVK vs. native D3D11 performance, so it sums up to something worse. :) I could bisect it to this commit: https://github.com/mesa3d/mesa/commit/0a313cc285c2939de9cac07f045b0b699bc208ca With it reverted, performance in mesa-master is normal. Is there a chance to make CTS dEQP-VK.pipeline.depth_range_unrestricted.* pass without causing the performance regression? This is unfortunately unchanged with latest master: ~148fps where it was ~162fps. amdvlk scores ~155fps, and with pageflipping + amdgpu.dc=0 ~160fps I can't workaround this anymore by reverting 0a313cc285c2939de9cac07f045b0b699bc208ca, as radv stopped building successfully without it. Should be fixed by https://gitlab.freedesktop.org/mesa/mesa/merge_requests/2025 Confirmed, performance is back to >160fps. Thanks a lot, your efforts are really outstanding! Can you please wait before closing tickets? Sending a change doesn't necessarily mean that it will be pushed/accepted. Thanks! Of course, sorry. Can you please pull the MR and try again? Does the performance regression is still fixed? I would say yes, just want a confirmation. With the updated MR, performance unfortunately is worse again. Okay, that's unfortunate but I prefer correctness vs performance. I will wait for the MR to be reviewed and let you know what happens. -- 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/863. |
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.