just like everything else ... randomly!

(unless you are one of the teachers pets!)

Yes, it is a 64 bit machine. But that should not matter (see below).



That post talks only about the various scenarios, where redundant tasks are sent out. It does not talk about how credits are awarded when there are no redundant tasks. For all but one of the examples I listed above, they were quorum of 1. No second task was sent. So why was the amount awarded different (less) than the amount claimed?

The reason is that the claimed credits are determined by the boinc manager based on your benchmark score & the time spend. The benchmark is based on int & float calculations. On a 64bit machine the 32bit integer benchmark run quicker, giving you a higher benchmark score than with the same hardware but a 32bit OS. However since HFCC is primarily float, you don't actually process the workunit quicker than the same hardware with 32bit OS, while your claimed credits are higher.

In redundant projects this is handled by comparing your claimed credits to the claimed credits of your wingmen. In zero-redundancy this obviously isn't possible. Therefore these tasks run a tiny benchmark as part of the workunit, and this benchmark score is reported to the validator. As this benchmark is HFCC specific it obviously primarily does float calculations, resulting in a lower score than the benchmark done by the boinc manager, resulting in a lower granted credit than the claimed credit.


In short: The claimed credit is incorrect because you run 32 bit float tasks on a 64bit OS.

zombie67,

See I told you the points were just randomly assigned!

It is Magic