The present credit plan is in place since Week 1 November 2006 and was advised in this thread: http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=9545

BOINC has no reference computer. The computational capacity is tested and expressed in values of Whetstone and Dhrystone. Add those 2 up and divide by 480 to get the hourly claim.

If the benchmark is run when the computer is truly idle, the value can be considerably higher than when it's run when watching streaming video or doing other intensive work in other words 'when thecomputer is really used'. The only thing one can do is to switch off all applications except BOINC, go to the advanced menu and force a benchmark run. That should temporarily increase the value.

The averaging and outlier rules are designed to stop people from manipulating the test values. The data is logged and in arrears it can be seen if a hourly claim 'fits' to a particular CPU and OS. Each time a work unit result is returned, the CPU details, video card and OS info is send to the servers.

Many projects ignore the claim all together. They use predetermined credits based on flop counts for each work unit or batch.

If u decide to manually benchmark, make sure the 'leave in memory' option has been selected in the device profile. Each time a test is done, the work unit would otherwise restart from the last checkpoint saved, loosing computation time!

Edit: Consolidated the double post and deleted the second.

Are u posting credit or are you posting claim?

What about the third machine?

Only with the 3rd result returned will the average be computed and the credit awarded. Depending on what the 3rd claims, your awarded credit will go up.

Added: There's nothing unfair about the 'wanted' credit. At the end of the day u would be claiming for 24 hours of crunch - per core - 2.30 times more than the other device. On a dual core versus a single core like the one with the 71.3 claim, u have 4.60 times more claim. Given the median system, it's likely that on this particular job the credit will actually work out favourable to u i.e. higher than 54.2.

Edit: Corrected calculation and replaced 'median' with 'average'

Hello winterM,
You are claiming about twice as much credit per hour as the other member did. Are you arguing that HE is being treated unfairly? Different CPUs run integer operations and floating point operations at different speeds. The BOINC method of averaging both types of operations will never score work units with exact accuracy unless the work units require a fixed ratio of integer ops to floating point ops.
Also, the UD credit scores are capped. That credit formula was created years ago. UD will earn you far fewer points than BOINC.

Lawrence

Your benchmark seems a little on the low side, maybe 10% lower than I would expect from a E6700 running at stock speed. You can run it again manually, several times if need be to see if it can do better. Maybe check the task manager for any processes that are hogging CPU cycles.