Author |
Message |
|
Hello, should i install these new driver packge to get more crunshing performance ?
Using 2x 460 GTX.
Any guesses ?
Thread can be canceled ! See right now thats only for Windows 7, sorry |
|
|
MarkJ Volunteer moderator Volunteer tester Send message
Joined: 24 Dec 08 Posts: 738 Credit: 200,909,904 RAC: 0 Level
Scientific publications
|
Hello, should i install these new driver packge to get more crunshing performance ?
Using 2x 460 GTX.
Any guesses ?
Thread can be canceled ! See right now thats only for Windows 7, sorry
Just because they are beta drivers doesn't mean they are faster than the previous version. Its usually to support new hardware or fix bugs.
I personally wait until they become WHQL before updating and even then they sometimes stuff up (look at the 295.x and 296.x drivers that introduced the monitor sleep bug).
Having said that feel free to instal them and keep an eye on your first couple of work units to see how they go. If it stufs up or your crunch times are slower you can always reinstall the older drivers. Let us know how it goes.
____________
BOINC blog |
|
|
|
Side note: do newer drives not have the monitor sleep bug anymore? Didn't expect nVidia to fix it this soon.. :p
MrS
____________
Scanning for our furry friends since Jan 2002 |
|
|
5potSend message
Joined: 8 Mar 12 Posts: 411 Credit: 2,083,882,218 RAC: 0 Level
Scientific publications
|
I did testing on the earlier 3 series drivers and could not replicate the bug. I have download these new drivers as well since they fix some serious bugs for kepler owners. So far so good. % utilization seems the same. |
|
|
skgivenVolunteer moderator Volunteer tester
Send message
Joined: 23 Apr 09 Posts: 3968 Credit: 1,995,359,260 RAC: 0 Level
Scientific publications
|
Please NO - do not install Beta drivers unless you are willing to take the risks of loss of functionality, operating system problems and hardware failures!
I 'tested' a 302.x driver recently. Immediately after installing it my monitor started realigning itself, repeatedly. In less than two days the monitor was dead. Basically it was like someone turning the light on and off repeatedly, until it popped - It was a fairly expensive 24" too! As well as potentially fixing bugs, beta drivers can introduce problems.
Generally speaking new drivers only improve some gaming performance, fix bugs, introduce new features or remove features/functionality. Usually new drivers offer no improvement for CUDA crunching and are often slower for crunching.
WRT GPUGrid crunching the only times you should update a driver is if the one you have is causing problems or the one you are using is outdated; can't be used to crunch any more following a major application update (perhaps once every 6 to 12 months). When there is an app update it's usually to use a more refined/feature rich version of CUDA or facilitate new GPU's. If an app uses CUDA 4.2 and a driver introduces compatibility for CUDA 5, for example, the driver will not improve the CUDA 4.2 app's performance. Even a new version of CUDA does not necessarily improve the app; there might not be anything in the latest CUDA version for GPUGrid.
____________
FAQ's
HOW TO:
- Opt out of Beta Tests
- Ask for Help |
|
|
|
I did it, but...
BOINC mananger dont want SLI configuration any more.
processes have been broken, after i disabled SLI everythings running fine :o |
|
|
5potSend message
Joined: 8 Mar 12 Posts: 411 Credit: 2,083,882,218 RAC: 0 Level
Scientific publications
|
Yes skgiven.
Sorry, should have been more clear in regards to the bugs that were fixed. Mostly gaming in regards to the vsync stutter bug, but one was due to the previous drivers being stuck at the 50Mhz clocks.
If you are only crunching on your rig. I would wait. They are trying to get the next WHQL out as soon as they can to push the vsync update most likely towards the end of this month.
Cheers |
|
|
|
I have been using it (340...) for a couple of days with 680GTX and 570GTX ant it seems to work fine. |
|
|