Comment 3 for bug 294925
Revision history for this message
| Rocko (rockorequin) wrote Re: nvidia 3D/compiz performance is greatly reduced in Intrepid | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Using Call of Duty 4 running under wine 1.1.7 as a benchmark, both 173.14.12 and 177.80 are much slower than Hardy with 173.14.12.
Intrepid only manages 10-13 fps (at the start of the 'War Pig' level) with either driver, while Hardy gets around 28-30 fps, ie over double the rate. This is running in 1680x1050 resolution on a second monitor (COD4 settings are identical in both Intrepid and Hardy).
So 3D in Intrepid is much slower than Hardy with *both* nvidia drivers for this game.
I just re-did the results for OpenArena with Intrepid's 173.14.12 driver and got vastly slower results than last time:
840 frames 3.1 seconds 272.6 fps 1.0/3.7/23.0/1.8 ms
840 frames 3.0 seconds 282.1 fps 1.0/3.5/41.0/1.9 ms
840 frames 3.0 seconds 280.7 fps 1.0/3.6/14.0/1.4 ms
840 frames 3.0 seconds 281.6 fps 1.0/3.6/13.0/1.4 ms
nvidia-settings confirms that the 173.14.12 driver is running. Is it possible that the problem is in the non-kernel driver and part of 177.80 has been left in userspace? I'm using envyng to change drivers and at one point after rebooting it had reverted to the 177.80 kernel driver without my asking it.
Also, I tried both OpenArena and COD4 with compiz disabled and the same results. So perhaps Intrepid's poor 3D performance should be listed against something like xorg-server 1.5? What's the best way to debug something like this?