nV News Forums - 304.37: Terrible performance regression

nV News Forums (http://www.nvnews.net/vbulletin/index.php)

- NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)

- - 304.37: Terrible performance regression (http://www.nvnews.net/vbulletin/showthread.php?t=188157)

304.37: Terrible performance regression

Updating from 304.22 to 304.37 destroys all possibility of using any application GPU demanding, i can't play WoW or Diablo 3, the framerate droped from 50-60 fps to 5-10 fps, it's totally unplayable!!!

I have a Core i5 with Gentoo: gcc-4.6.3, glibc-2.15-r2, Kernel 3.5.0-gentoo x86_64

And the GPU is a GT 240

P.S: Oh, i forgot the report log

Re: 304.37: Terrible performance regression

I am running 304.37 under gentoo

$ glxgears
46641 frames in 5.0 seconds = 9328.183 FPS
46814 frames in 5.0 seconds = 9362.695 FPS
43926 frames in 5.0 seconds = 8785.135 FPS
43302 frames in 5.0 seconds = 8660.307 FPS
46932 frames in 5.0 seconds = 9386.398 FPS

All seems normal. What graphic card do you have?

Re: 304.37: Terrible performance regression

Some people are reporting that the GT 240 is locked in a low performance mode.

Roll back to a previous driver version and wait for a fix.

E-mail your bug report (including the log) to linux-bugs@nvidia.com, as devs don't visit the forums anymore.

Re: 304.37: Terrible performance regression

Thanks, i've send the email.

Re: 304.37: Terrible performance regression

Quote:

Originally Posted by johnc (Post 2571537)

as devs don't visit the forums anymore.

So that's why this place feels like a ghost town. I hope it has nothing to do with the Linus thing. Though I do note it's the top sticky ... it's probably so.

Re: 304.37: Terrible performance regression

It has everything to do with the fact that NVIDIA's own forums were hacked two months ago and they are contemplating the forums future.

Re: 304.37: Terrible performance regression

Quote:

Originally Posted by artem (Post 2571553)

It has everything to do with the fact that NVIDIA's own forums were hacked two months ago and they are contemplating the forums future.

BTW.: I couldn't access the forum for a couple of weeks after the hack. Somebody else had the same experience?

regards

Bernhard

Re: 304.37: Terrible performance regression

Txema, 304.37 has "Sync to VBlank" (OpenGL Settings) enabled by default; try to disable it.

Re: 304.37: Terrible performance regression

Quote:

Originally Posted by Txema (Post 2571534)

The same in my case - GT220, this is my thread: http://www.nvnews.net/vbulletin/showthread.php?t=188366 - very bad performance while deinterleacing video. I have "Sync to VBlank" enabled in older driver as well.

Re: 304.37: Terrible performance regression

I forgot to post the reply to my email:

Quote:

We recently became aware of a regression that prevents the GeForce GT 240, and possibly other cards (GT 240 is the only one we're aware of right now) from raising its clocks to the maximum performance level. The regression window you report (304.22 good; 304.37 bad) matches our observations for this issue, which might be responsible for the poor performance you are experiencing. This regression is currently under investigation.

Can you confirm, by monitoring the "PowerMizer" page in the nvidia-settings control panel, that your GPU does not raise its clocks to the maximum level with 304.37, but is able to do so in 304.22?

Thanks,
Daniel

And after confirming it:

Quote:

Yes, that does sound like the PowerMizer issue we're investigating. Thanks for confirming; for your reference, we are tracking this as NVIDIA bug 1038281, in case you want to make inquiries about this bug in the future.

So, no, it has nothing to do with Sync to vblank (wich i had enabled before this release because i want it)

Re: 304.37: Terrible performance regression

How to create log to send to nvidia support? Is there any script to do this?

Re: 304.37: Terrible performance regression

The driver install script should install the bug report utility somewhere in your path. Try opening a terminal and fire off this command:

Code:

nvidia-bug-report.sh

As described in the sticky.