Hmmm, seems its the machine, not the WU's - looks like the 8-core Clovertown machine is claiming low for these new HCC units even though the Boinc Integer Benchmark is higher due to 64bit:

Ghost 3, Q6600 @ 3.42GHz, XP 32bit - Benchmark 3358 FP, 7419 Integer:



Clovertown, 2 x E5340 @ 3GHz, Windows Server 2003 64bit - Benchmark 2851 FP/ 9251 Integer :



Ghost3 is claiming its usual 20 credit/hour the same as DDDT/FAAH, but the Clovertown is only claiming 12 credit/hour with these new 5.20's.

The Clovertown claimed higher on the old 5.15 WU's - around 20 credit/hour:




Methinks my Dual-CPU machine may not be the best thing to run on this project if I was looking for points.

I understand what you mean about creating a 'history' - but surely that only effects the Granted Credit side? What is puzzling here is that the initial credit claim seems low now, which as you can see from the following example result, is penalising the other machine in the quorum by dragging their granted credit down:



Obviously there may be times as history grows that I may benefit from getting the other persons higher credit claim, but if the past is anything to go by, it tends to get rounded down more often than not.

I'm struggling to understand what you mean exactly I'm afraid Sek

Are you saying that the benchmark claim from the machine would have been OK, but by the time it appears in results status it has somehow been adjusted - in this case lower?

Thanks Sek

In which case how does this happen? - as surely the original claim would normally be reported correctly regardless of how outrageous or inflated, but it is the granted credit that gets adjusted?

Is this an issue with my machine or somewhere else?........or is it actually an issue as such at all

If it is a issue - is it being looked at within your 'back-room' thread by the Techs?

So you cloverleaf wearing crunchers are now officially happy too