Ridiculously low GPU scores assigned

Message boards : Number crunching : Ridiculously low GPU scores assigned
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile pantheman

Send message
Joined: 6 Nov 01
Posts: 3
Credit: 1,169,965
RAC: 2
Belgium
Message 1696401 - Posted: 28 Jun 2015, 10:06:28 UTC
Last modified: 28 Jun 2015, 10:07:14 UTC

Any idea why the score for seti@home on both intel and nvidia gpu's is ridiculously low? I mean crunching f.e. collatz conjecture gets me 200 to 500 times the amount of boinc credits for the same amount of crunching time on the same hardware. This makes the seti project veeery unattractive and I love this project as it was the first one I started (even from the time there was no boinc yet).

EDIT: even worse: the score for GPU is about the same as for CPU. Seems odd.
ID: 1696401 · Report as offensive
Profile jason_gee
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 24 Nov 06
Posts: 7489
Credit: 91,093,184
RAC: 0
Australia
Message 1696402 - Posted: 28 Jun 2015, 10:15:11 UTC - in response to Message 1696401.  
Last modified: 28 Jun 2015, 10:17:18 UTC

basically in the case of multibeam applications, the credit is normalised to the cobblestone scale, but the reference application is a CPU AVX enabled application. Buried underneath is the use of Boinc Whetstone, which is not a vectorised form. As most CPU's these days will have SSE or higher, and the applications optimised, the last 100 results for the CPU application that set these scales will 'claim' between ~1/2x to ~1/4x what they should be, then the GPU variants are normalised to that.

For astropulse there isn't an AVX stock version AFAIK, so that'll be roughly ~1/2x (50%)

Also there seems to be a lot of noise in the credit system, to the tune of > +/-30%. If you're like me, at odds with Murphy, you'll tend to receive on the lower end of that noise.
"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.
ID: 1696402 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14650
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1696404 - Posted: 28 Jun 2015, 10:39:48 UTC

Added to which, comparisons to other projects often fail because some projects have stopped even paying lip-service to the cobblestone scale. If the normalisation and variance issues Jason mentions are ever rectified, it might be possible to persuade other projects to return to the official definition of credit, so that comparisons once again become meaningful. But that time may still be some way off.
ID: 1696404 · Report as offensive
Profile pantheman

Send message
Joined: 6 Nov 01
Posts: 3
Credit: 1,169,965
RAC: 2
Belgium
Message 1698072 - Posted: 3 Jul 2015, 9:16:42 UTC

OK I can understand that there can be some deviation and up to 75% less credit is no problem for any truthful volunteer, but a factor of >99% is simply too great. This hurts Seti@home as some users will abandon the project simply for better boincstat scores.
ID: 1698072 · Report as offensive
Profile HAL9000
Volunteer tester
Avatar

Send message
Joined: 11 Sep 99
Posts: 6534
Credit: 196,805,888
RAC: 57
United States
Message 1698186 - Posted: 3 Jul 2015, 16:11:06 UTC - in response to Message 1698072.  

OK I can understand that there can be some deviation and up to 75% less credit is no problem for any truthful volunteer, but a factor of >99% is simply too great. This hurts Seti@home as some users will abandon the project simply for better boincstat scores.

Well those that are after useless made up point may do that, but many users of SETI@home are here for the science to find ETI.
SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[
ID: 1698186 · Report as offensive
rob smith Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer moderator
Volunteer tester

Send message
Joined: 7 Mar 03
Posts: 22190
Credit: 416,307,556
RAC: 380
United Kingdom
Message 1698215 - Posted: 3 Jul 2015, 16:53:49 UTC

Credit scores per task per task really cannot be compared between projects. Put it simply, some projects throw credits over the wall like confetti at a wedding, others give a fixed score per task, and others are even more parsimonious with credits than SETI. Use them to compare your performance over time within a project by all means, but don't expect to be able to compare between projects.
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?
ID: 1698215 · Report as offensive
qbit
Volunteer tester
Avatar

Send message
Joined: 19 Sep 04
Posts: 630
Credit: 6,868,528
RAC: 0
Austria
Message 1698236 - Posted: 3 Jul 2015, 19:12:37 UTC

It's not just between projects, credit screw is also extremly inconsistent within Seti.

While comparing my AP tasks with those from other users with a GTX 750 I discovered something really strange. This are results from one of those users:

http://i.imgur.com/7VYTz3Y.png

The first strange thing is that there are tasks with lesser runtime that give more credit then those with higher runtime. But I guess we've all seen that. But the second strange thing are the overall high scores. For comparison, here's an actual screenshot from my results:

http://i.imgur.com/O3kzkmr.png

I guess you can see the difference.

Now I'm in here for the science and I know those credits aren't worth anything, but still I'm curious. Any thoughts on this?
ID: 1698236 · Report as offensive

Message boards : Number crunching : Ridiculously low GPU scores assigned


 
©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.