Calculation time GTX 580 vs GTX 680

Message boards : Number crunching : Calculation time GTX 580 vs GTX 680
Message board moderation

To post messages, you must log in.

AuthorMessage
Mark Lybeck

Send message
Joined: 9 Aug 99
Posts: 245
Credit: 216,677,290
RAC: 173
Finland
Message 1307511 - Posted: 18 Nov 2012, 21:53:23 UTC

Hello,

I did an interesting finding on the calculation time reported by SETI. I have now in the same computer both GTX 580 and GTX680.

The finding is that for GTX 580 the reported calculation time for one WU is roughly 1100 seconds while for the GTX 680 the calulation time averages around 250 (4,2 minutes) seconds.

When checking the Boinc Manager Tasks tab on active work Units the average calculation time for a WU is roughly 20 minutes (=1200s) (3 WU concurrently per card). So the calculation time reported is more in line with the GTX 580.

Why is the reported calculation time for GTX 680 differing so much?
Is GTX 680 idling somewhere and this is not reported in correctly?


http://setiathome.berkeley.edu/results.php?hostid=3299266&offset=0&show_names=0&state=2&appid=

ID: 1307511 · Report as offensive
Team kizb

Send message
Joined: 8 Mar 01
Posts: 219
Credit: 3,709,162
RAC: 0
Germany
Message 1307519 - Posted: 18 Nov 2012, 22:25:56 UTC

So If I read this correctly:

580 is doing one WU in about 18 min

680 is doing one WU in about 4 min

Each doing 3 WU's at a time.

Looks like the 680 is completing WUs MUCH faster! As far as the average, it would be just that, an average overall. So if you where running the 580 alone for say 1000 WUs in that rig before adding the 680 and have only completed 100 WUs, the average is going to remain high since its taking an overall average off all the WUs.

A really good true test would be to setup two new rigs, then put the 580 in one and the 680 in the other. There may be an easier way to reset the average as well,
My Computers:
â–ˆ Blue Offline
â–ˆ Green Offline
â–ˆ Red Offline
ID: 1307519 · Report as offensive
juan BFP Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 16 Mar 07
Posts: 9786
Credit: 572,710,851
RAC: 3,799
Panama
Message 1307536 - Posted: 18 Nov 2012, 23:05:14 UTC
Last modified: 18 Nov 2012, 23:05:56 UTC

Just a warning, to make that test you need 2 exactly equals WU, the processing times changes from 4 to 15 minutes (even on the same GPU) easely because the AR.

Your times are in the normal ranges...at least compared with mines on similar boards.
ID: 1307536 · Report as offensive
Profile S@NL - eFMer - efmer.com/boinc
Volunteer tester
Avatar

Send message
Joined: 7 Jun 99
Posts: 512
Credit: 148,746,305
RAC: 0
United States
Message 1307709 - Posted: 19 Nov 2012, 14:26:03 UTC - in response to Message 1307511.  

Hello,

I did an interesting finding on the calculation time reported by SETI. I have now in the same computer both GTX 580 and GTX680.

The finding is that for GTX 580 the reported calculation time for one WU is roughly 1100 seconds while for the GTX 680 the calulation time averages around 250 (4,2 minutes) seconds.

When checking the Boinc Manager Tasks tab on active work Units the average calculation time for a WU is roughly 20 minutes (=1200s) (3 WU concurrently per card). So the calculation time reported is more in line with the GTX 580.

Why is the reported calculation time for GTX 680 differing so much?
Is GTX 680 idling somewhere and this is not reported in correctly?


http://setiathome.berkeley.edu/results.php?hostid=3299266&offset=0&show_names=0&state=2&appid=

Here is a list:
http://www.efmer.eu/forum_tt/index.php?topic=981.0
Try the program and report back the best time.
TThrottle Control your temperatures. BoincTasks The best way to view BOINC. Anza Borrego Desert hiking.
ID: 1307709 · Report as offensive

Message boards : Number crunching : Calculation time GTX 580 vs GTX 680


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.