Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 2
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1366 times and has 1 reply Next Thread
Thyme Lawn
Cruncher
Joined: Dec 9, 2008
Post Count: 46
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Claimed credit inflation for some FAHV tasks

In the absence of DSFL and SN2S work I started running FA@H on my laptop (C2D T7300, BOINC 6.12.33) a couple of weeks ago. I've spotted that a couple of my FAHV tasks have claimed (and been granted) a lot more credit than normal.

FAHV tasks are mostly running for between 1.5 and 2.5 hours, claiming 17 to 25 credits and being granted fairly close to the claim. The task I ran from WU 749391284 (FAHV_ x3NFA_ B_ IN_ Y3_ 0047351_ 0964_2) had 1.69 hours CPU time and 2.53 hours elapsed time, claimed 198.1 credits and was granted 106.9 (the wingman _3 task claimed 15.8). The task ran without interruption and the elapsed time was extended because the laptop was running higher priority (i.e. non BOINC) CPU intensive work at the same time.

By way of comparison, the laptop's most recently reported faah task ran for 12.83 hours and claimed 161.4 credits.

This suggests there could be a problem with the way the credit claim is being determined for some FAHV tasks.
----------------------------------------
"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer
[Aug 3, 2013 1:05:02 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Claimed credit inflation for some FAHV tasks

"Suggests"? Today, tomorrow, the day after, no takers to expand and at this heat, strongly ill advised... the system fill in the blanks, has been broken for as long as I can remember, within a science, across sciences and recently pegged it the OAB. It got substantially worse with server v7 Berkeley system, in that I'd not be surprised if the 32 bit [long running] FAAH is pooled with the 64 bit [short and fast running] FAHV, at least it's so bad [for me], my 2670QM is made to resemble a ZX80... an antique, so be kind to all, quickly turn this page and forget it. shock
[Aug 3, 2013 1:46:32 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread