Bug 85580 - [RadeonSI] Bad performance in TF2.
Summary: [RadeonSI] Bad performance in TF2.
Status: RESOLVED WORKSFORME
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/radeonsi (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-29 03:25 UTC by Aaron B
Modified: 2015-07-07 02:48 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Aaron B 2014-10-29 03:25:38 UTC
I built Mesa just a few days ago with LLVM 3.5, git mesa, 3.18-rc2 kernel. Performance is just horrible with tons of dips when playing TF2, and probably other Valve games. Polygon count just makes it too heavy to what it used to be, dipping down to 20FPS or so when moving objects and such. I don't have time to bisect, don't even know how much longer I will be using this R9 270X, so any tests I can do without a recompile I can try. Benchmarks like glmark2 are fine, but in-game performance is just bad.
Comment 1 Michel Dänzer 2014-10-29 08:23:07 UTC
(In reply to Aaron B from comment #0)
> Polygon count just makes it too heavy to what it used to be, dipping down to
> 20FPS or so when moving objects and such.

Have you double-checked that direct rendering and hardware acceleration are working for 32-bit processes? Did you build 32-bit Mesa as well?


> I don't have time to bisect, [...]

So it's a regression? In what kind of time-frame?
Comment 2 Aaron B 2014-11-02 01:14:51 UTC
It has gotten better since I've re-compiled llvm and mesa, and moved back to just 3.5. But it still drops down to the red in the source engine FPS counter a lot still. It should be a regression, afaict, it never did it as often as it does with llvm 3.5, current mesa, radeonsi.
Comment 3 Aaron B 2015-07-07 02:48:39 UTC
Probably fixed eventually, never tested but going to just close assuming it's fixed since it's the biggest linux game really.


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.