#Boinc credits 32 bit#
In short: The claimed credit is incorrect because you run 32 bit float tasks on a 64bit OS. 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. When at least two results have been returned, the server compares them. When a computer reports a result, it claims a certain amount of credit, based on how much CPU time was used.
![boinc credits boinc credits](https://pimylifeup.com/wp-content/uploads/2016/06/statistics-screen-610x336.png)
Therefore these tasks run a tiny benchmark as part of the workunit, and this benchmark score is reported to the validator. To ensure that credit is granted fairly, most BOINC projects work as follows: Each task may be sent to two computers. In zero-redundancy this obviously isn't possible. In redundant projects this is handled by comparing your claimed credits to the claimed credits of your wingmen. 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. 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. The benchmark is based on int & float calculations. Specific optimizations for our processor architecture (see here).The reason is that the claimed credits are determined by the boinc manager based on your benchmark score & the time spend.
#Boinc credits code#
This is the reason we can achieve such dramatic improvements by recompiling the BOINC source code with On and can make a significant difference to raw performance.įinally, the BOINC client and contained benchmark code are not optimized for any specific processor architecture, but rather use generic i686 optimizationsįor broad compatibility with a wide range of hardware. Thirdly, none of these estimates or benchmarks take into account factors such as memory bandwidth or processor cache size which SETI is hugely dependant SETI performs almost all single precision maths and typically only spends about 20% of it's time performing trigonometric functions. The Whetstone benchmark tests double precision maths and spends the majority of it's time performing trigonometric functions whereas Secondly, BOINC uses the Whetstone benchmark to estimate floating point math performance of your computer. This is the reason some units process significantly quicker than others. Whetstone benchmark as an indicator of floating point math performance of your computer.įirstly, SETI estimates the number of floating point operations for it's work units,īut this estimation is the same for each unit where in reality this is not the case.
#Boinc credits update#
What messages are shown in the BOINC Manager when you update to Rosetta Does it say it is requesting new work Thank you Mod.Sense: As I have shut down computer since, I have not got exact. DB Status Ready to send: 40,032 Question: Why cant I get any WUs to crunch. The estimated time is based on two other estimates, the number of floating point operations required to process the work unit and the Credit: 107,245 RAC: 0: Message 65640 - Posted:, 18:17:08 UTC. The time estimated by BOINC for a work unit to process on your computer is often not very accurate and there are a number of reasons for this. Why Estimated CPU Time is Not Very Accurate The Dhrystone Benchmark tests repeated integer operations together with several operating system file handling operations.Ĭlaimed credit is calculated as a function of the Whetstone and Dhrystone benchmarks calculated by theīOINC application multiplied by the time taken in seconds to process the work unit using the following formula:Įstimated time (Sec) = 27,900,000/Whetstone Such as sine, cosine, tangent and exponents.
![boinc credits boinc credits](http://www.p-s-soft.at/current/images/04_content_boinc_00.jpg)
The tests include simple addition, subtraction, multiplication and division of floating point numbers together with trigonometric functions
![boinc credits boinc credits](https://boinc.berkeley.edu/trac/raw-attachment/wiki/CreditStats/stats.png)
It performs 8 groups of tests multiple times and gives a score based on the number of operations performed divided by the time taken. The Whetstone benchmark tests double precision floating point operations. The highest and lowest claimed credit values are discarded and the average (mean) of the remaining values is awarded to all users.įor three successful results, this is usually just the middle value of the three claimed credits. The results are then validated against at least two other results returned by other users. When you return the result to the BOINC project servers together with your claimed credit, These benchmark scores are then used in conjunction with the time taken to process a work unit to calculate how much credit your computer will claim for that work unit.īut you are not simply granted the credit you claim. The BOINC application uses two benchmarks, Whetstone and Dhrystone, to measure the floating point and integer speed of your computer. The amount of credit you will get for each processed work unit depends on a number of factors. BOINC uses a new credit system rather than simply counting the number of results returned.īOINC's new unit of credit is called the Cobblestone, named after Jeff Cobb of the Project.