question about claimed credit

Message boards : Number crunching : question about claimed credit
Message board moderation

To post messages, you must log in.

AuthorMessage
uba36
Volunteer tester

Send message
Joined: 17 Jul 02
Posts: 74
Credit: 1,159,280
RAC: 0
Germany
Message 50464 - Posted: 1 Dec 2004, 20:27:40 UTC
Last modified: 1 Dec 2004, 20:30:40 UTC

Why does the fastet machine does't claim the highest credit? See link: WU 4772040 Just compare CPU time and claimed credit!
ID: 50464 · Report as offensive
Profile Keck_Komputers
Volunteer tester
Avatar

Send message
Joined: 4 Jul 99
Posts: 1575
Credit: 4,152,111
RAC: 1
United States
Message 50469 - Posted: 1 Dec 2004, 20:52:13 UTC

Theoretically all computers should claim very nearly the same credit for the same workunit.

The benchmarking code needs some work even though it does work much better now than it has in the past. It also may be impossible to get really accurate numbers due to the way newer processors slow themselves down to prevent overheating.
BOINC WIKI

BOINCing since 2002/12/8
ID: 50469 · Report as offensive
Ned Slider

Send message
Joined: 12 Oct 01
Posts: 668
Credit: 4,375,315
RAC: 0
United Kingdom
Message 50580 - Posted: 2 Dec 2004, 3:17:23 UTC

Credit is claimed according to the following formula:

claimed credit = ([whetstone]+[dhrystone])/1000 * 100 / (2 * secs_per_day) * wu_cpu_time

or to simplify the equation, claimed credit = ([whetstone]+[dhrystone]) * wu_cpu_time / 1728000

Note: wu_cpu_time is the time taken to process the unit in seconds.

Ned


*** My Guide to Compiling Optimised BOINC and SETI Clients ***
*** Download Optimised BOINC and SETI Clients for Linux Here ***
ID: 50580 · Report as offensive
Profile blocko
Volunteer tester
Avatar

Send message
Joined: 4 May 00
Posts: 2
Credit: 502,607
RAC: 0
Australia
Message 51748 - Posted: 6 Dec 2004, 11:57:58 UTC - in response to Message 50580.  

Why then does my silly computer keep claiming zero credits for every workunit? Thankfully SETI see through my computer's false modesty and hand out a seemingly reasonable number of ~30 per unit.

> Credit is claimed according to the following formula:
>
> claimed credit = ([whetstone]+[dhrystone])/1000 * 100 / (2 * secs_per_day) *
> wu_cpu_time
>
> or to simplify the equation, claimed credit = ([whetstone]+[dhrystone]) *
> wu_cpu_time / 1728000
>
> Note: wu_cpu_time is the time taken to process the unit in seconds.
>
> Ned
>
>
>
<img src="http://www.setisynergy.com/images/stats/comb-516.jpg" />
ID: 51748 · Report as offensive
Profile Keck_Komputers
Volunteer tester
Avatar

Send message
Joined: 4 Jul 99
Posts: 1575
Credit: 4,152,111
RAC: 1
United States
Message 51762 - Posted: 6 Dec 2004, 16:29:58 UTC

>Why then does my silly computer keep claiming zero credits for every
>workunit? Thankfully SETI see through my computer's false modesty and hand
>out a seemingly reasonable number of ~30 per unit.

Try rerunning your benchmarks manually. The last automatic run may have had problems.
BOINC WIKI

BOINCing since 2002/12/8
ID: 51762 · Report as offensive
Divide Overflow
Volunteer tester
Avatar

Send message
Joined: 3 Apr 99
Posts: 365
Credit: 131,684
RAC: 0
United States
Message 51768 - Posted: 6 Dec 2004, 17:59:21 UTC - in response to Message 51748.  
Last modified: 6 Dec 2004, 17:59:59 UTC

> Why then does my silly computer keep claiming zero credits for every workunit?
> Thankfully SETI see through my computer's false modesty and hand out a
> seemingly reasonable number of ~30 per unit.

Your computers are hidden, so we can't see any information on what client version and computer type you have. What are the basics of your system? CPU, OS, BOINC version? Anything exotic going on that would produce the nonstandard response?

Since BOINC takes the middle claimed credit value and awards it to all validated results as awarded credit, the fact that your machine claims 0 means it can be hurting the credit scores being granted out there. If even just two people in your same situation were to be assigned the same WU, you would all be given 0 credit for successfully completing the WU! This is a flaw in the credit system, and accurate benchmarking should be an important issue for the project.


ID: 51768 · Report as offensive
Profile Paul Knibbs

Send message
Joined: 21 Mar 01
Posts: 5
Credit: 194,839
RAC: 0
United Kingdom
Message 51795 - Posted: 6 Dec 2004, 22:21:11 UTC

Amen to that--see my thread about a machine with a benchmark of 113,000! I reckon the claimed credit is going be 1000+ on that one...
ID: 51795 · Report as offensive
Profile blocko
Volunteer tester
Avatar

Send message
Joined: 4 May 00
Posts: 2
Credit: 502,607
RAC: 0
Australia
Message 51943 - Posted: 7 Dec 2004, 8:01:36 UTC

OK I'll try manually re-running my benchmarks.
I'll unhide my computer so you can stickybeak, but as far as I know it is a stock-standard PC. Nothing weird at all.

--- - 2004-12-07 18:59:13 - Running CPU benchmarks
--- - 2004-12-07 19:00:14 - Benchmark results:
--- - 2004-12-07 19:00:14 - Number of CPUs: 1
--- - 2004-12-07 19:00:14 - 526 double precision MIPS (Whetstone) per CPU
--- - 2004-12-07 19:00:14 - 1310 integer MIPS (Dhrystone) per CPU
--- - 2004-12-07 19:00:14 - Finished CPU benchmarks

OK done - nothing weird there.
Looks the same as last time.

<img src="http://www.setisynergy.com/images/stats/comb-516.jpg" />
ID: 51943 · Report as offensive
Divide Overflow
Volunteer tester
Avatar

Send message
Joined: 3 Apr 99
Posts: 365
Credit: 131,684
RAC: 0
United States
Message 52079 - Posted: 7 Dec 2004, 23:51:56 UTC

Well, good news. Your last WU result actually claimed some credit. I'd pay attention to the next couple that go through, but it may have been a one time glitch.

ID: 52079 · Report as offensive

Message boards : Number crunching : question about claimed credit


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