Worst of all regressions was with the new Xserver, Mesa was about 20%
In my tests, I found that with Mesa 10.2/Kernel 3.13/Xserver 1.15, framerates were cut in half. Plymouth crashes with the early Linux3.14 rc1 that I tried, blocking my disk decryption system so I have yet to test the new kernel. With Mesa 10.2 but reverting to Xserver 1.14, I got back most of the regression but was still down 10-20%. That was the part that apparently turned out to by from hyper-z in my tests.
I got essentialy identical performance using Mesa 10.1 or Mesa 10.2 with hyper-z force-enabled in Critter (only one Z value, it's a 2d game) , but in Scorched3d,
R600_HYPERZ=1 scorched3d
locked up the whole x server with Hyper-Z and Mesa 10.2, with either version of X. I checked the exact same code with Mesa 10.1, no problems at all in Scorched3d.
I am guessing the issue with the new X server relates either to the DRI 3 changeover or to the rewrite of the GLX system referred to in the changelogs.
Originally posted by curaga
View Post
I got essentialy identical performance using Mesa 10.1 or Mesa 10.2 with hyper-z force-enabled in Critter (only one Z value, it's a 2d game) , but in Scorched3d,
R600_HYPERZ=1 scorched3d
locked up the whole x server with Hyper-Z and Mesa 10.2, with either version of X. I checked the exact same code with Mesa 10.1, no problems at all in Scorched3d.
I am guessing the issue with the new X server relates either to the DRI 3 changeover or to the rewrite of the GLX system referred to in the changelogs.
Comment