Message boards : Graphics cards (GPUs) : Gtx 680 errors
Author | Message |
---|---|
Hi there, | |
ID: 24339 | Rating: 0 | rate: / Reply Quote | |
See this thread: | |
ID: 24340 | Rating: 0 | rate: / Reply Quote | |
If you wish to crunch with one, the ONLY project that accepts them currently are primegrids sieve tasks. That's where I have mine until GPUgrid or WCG release their new app. | |
ID: 24343 | Rating: 0 | rate: / Reply Quote | |
Also works fine on Seti - mine has been happily crunching now for several weeks. | |
ID: 24365 | Rating: 0 | rate: / Reply Quote | |
Einstein just allowed several out for those using 300x, managed to grab some and report back that 300 series monitor sleep/resume does not seem to be an issue (VERY happy im off PrimeGrid) : ) | |
ID: 24366 | Rating: 0 | rate: / Reply Quote | |
If you wish to crunch with one, the ONLY project that accepts them currently are primegrids sieve tasks. That's where I have mine until GPUgrid or WCG release their new app. Einstein just allowed several out for those using 300x, managed to grab some and report back that 300 series monitor sleep/resume does not seem to be an issue Also works fine on Seti - mine has been happily crunching now for several weeks. Could you please compare the performance of your GTX 680 on those projects with older GTX cards (590, 580, 480)? | |
ID: 24373 | Rating: 0 | rate: / Reply Quote | |
On Einstein, it appears as though the program is designed for CC1.x so their site does not use its full potential and they can run multiple WU on one GPU w/ no way of knowing this on status page, but here are some results: | |
ID: 24374 | Rating: 0 | rate: / Reply Quote | |
As a side note. From what I've seen and read on non optimized projects at worst its a very efficient 580. Again once GPUgrid app is out I plan on running a much more extensive review with current setup, and another one at end of month. By then hopefully GPUgrid will have an OPTIMIZED app for 680 and not one it just "runs on". | |
ID: 24375 | Rating: 0 | rate: / Reply Quote | |
I've decided to not post differences in runtimes from Einstein, b/c it will be an irrelevant comparison. Their CC 1.x ALWAYS seem to finish around the same time for anything above a 560 (448). Whenever Windows is released, or if I can ever figure out this GRUB issue (haven't tried 12.04 yet but have it on USB), I will post 680 review using an i5@4.2 (of course w/ PCI2.0), and then I will do a review using Ivy i7 w/ PCI 3.0. | |
ID: 24392 | Rating: 0 | rate: / Reply Quote | |
Their CC 1.x ALWAYS seem to finish around the same time for anything above a 560 (448). Isn't that because their app needs some CPU support (actual calculations) rather than the app being able to run on CC 1.x?! MrS ____________ Scanning for our furry friends since Jan 2002 | |
ID: 24394 | Rating: 0 | rate: / Reply Quote | |
Yes, but i don't know of its the way its coded, or if gpus there have hit their "wall" but as I've said drawing comparisons between different high end gpus only matters when u load multiples and how many you.can load. I have heard that a 680 was up to 4 at a time, and I'm depleting stock to switch to 7.0.25 boinc and try this multi Wu thing out. I truly think GPUgrid will be best place to bench 680 crunching when it arrives. | |
ID: 24395 | Rating: 0 | rate: / Reply Quote | |
You're totally right about this, as long as you can'T tell how many WUs are run in parallel and the RAC hasn't stabilized, one can't tell how fast that machine really is. And comparing with just 1 WU at Einstein is pointless. Would probably be a CPU benchmark for high-end cards :p | |
ID: 24412 | Rating: 0 | rate: / Reply Quote | |
Have u also allready read about the "Red Screen of Death" ? | |
ID: 24453 | Rating: 0 | rate: / Reply Quote | |
Message boards : Graphics cards (GPUs) : Gtx 680 errors