Claimed Credit Problem

Message boards : Number crunching : Claimed Credit Problem
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile MikeSW17
Volunteer tester

Send message
Joined: 3 Apr 99
Posts: 1603
Credit: 2,700,523
RAC: 0
United Kingdom
Message 106072 - Posted: 1 May 2005, 9:40:41 UTC

Ummm, is there a problem?
Since upgrading to 4.35 yesterday, one of my systems is claiming Zero credit - even on 11,000 second work.

Here: http://setiweb.ssl.berkeley.edu/results.php?hostid=643488

7 results for 1st May (since 4.35) claim zero credit, yet one has been granted 25.

Only seems to be happening on this 1 system (of 4 - 3 on 4.35, 1 still on 4.25)

ID: 106072 · Report as offensive
Profile Dorsai
Avatar

Send message
Joined: 7 Sep 04
Posts: 474
Credit: 4,504,838
RAC: 0
United Kingdom
Message 106073 - Posted: 1 May 2005, 9:51:34 UTC
Last modified: 1 May 2005, 9:52:18 UTC

I don't know, but will hazard a guess it's something to do with the validater's & the current backlog that is building up of unvalidated results.

Once the system catches back up, you may find the claimed credit figure for those WU's that did not error in a few seconds to show a more reasonable figure.


Foamy is "Lord and Master".
(Oh, + some Classic WUs too.)
ID: 106073 · Report as offensive
Profile FalconFly
Avatar

Send message
Joined: 5 Oct 99
Posts: 394
Credit: 18,053,892
RAC: 0
Germany
Message 106074 - Posted: 1 May 2005, 9:58:52 UTC - in response to Message 106073.  
Last modified: 1 May 2005, 10:03:13 UTC

The actual Probem is here :
http://setiweb.ssl.berkeley.edu/show_host_detail.php?hostid=643488

The Benchmarks are either disabled on that host or an override is set (I've heard there are switches to allow the newer BOINC Clients to modify the Benchmarks).

With 0 MFlops FPU/ALU, I'd recommend to manually run Benchmarks again (that 'should' fix it) or look for similar related Problem Threads for the solution if it doesn't help.

For as long as the Benchmarks are 0, your System will always claim 0 Credit (x secconds CPU time multiplied by 0 will remain 0)

The only cause I could imagine leading to a Zero-Benchmark Result would be BOINC doing it while the System is under 100.0% load from other Applications (not getting any cycles), but it might be a quirrel with the used BOINC Version (after all, it remains a Beta for willing Users to test, likely still holding Bugs that cause funny things to happen).
ID: 106074 · Report as offensive
Profile MikeSW17
Volunteer tester

Send message
Joined: 3 Apr 99
Posts: 1603
Credit: 2,700,523
RAC: 0
United Kingdom
Message 106077 - Posted: 1 May 2005, 10:11:18 UTC - in response to Message 106074.  

> The actual Probem is here :
> http://setiweb.ssl.berkeley.edu/show_host_detail.php?hostid=643488
>

Well spotted, thanks FalconFly.

Benchmarks manually run - should fix it.

I hope this isn't an inherrent problem and mine was a one-off.
If the upgrade to 4.35 doesn't always correctly benchmark, it could cause a lot of complaints if a significant number of users claim zero and the validator gets them and grants zero. I only got credit because the other 3 claimed non-zero.


ID: 106077 · Report as offensive

Message boards : Number crunching : Claimed Credit Problem


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