BOINC Credit System

Within the BOINC platform for volunteer computing, the BOINC Credit System helps volunteers keep track of how much CPU time they have donated to various distributed computing projects. The credit system is designed to avoid cheating by validating results before granting credit on projects. This ensures users are returning accurate results for both scientific and statistical reasons.

Purposes for a credit system

Online distributed computing relies heavily, if not completely on volunteer computers. For this reason projects, such as SETI@home and other BOINC projects, depend on a complicated balance of long-term users and the cycle of new users and retiring users.

Reasons for participation

# Donate to scientific cause
#* Many users wish to advance the specific field of study
#* Projects that help fight disease may have an emotional connection for those participating
# Stress test computers
#* Processing distributed computing projects places a computer under continuous full CPU load, therefore, overclockers often use the stress to test their system's stability
# Teams, credits, and competition
#* Many individuals and teams run many computers and have some dedicated specifically to BOINC in hopes of climbing to the top of the world charts
# Personal benefits and recognition
#* Projects such as PlanetQuest plan on allowing individuals to name those planets discovered using their computers
#* Projects such as BURP plan on allowing users to submit their own 3D models to be rendered using BOINC

Cobblestones

The basis for the BOINC credit system is the cobblestone named after Jeff Cobb of SETI@home. The basis of the system is the concept that 100 cobblestones would be claimed for one day of work on a computer with the following specifications:
* 1,000 double-precision MIPS based on the Whetstone benchmark.
* 1,000 VAX MIPS based on the Dhrystone benchmark.

The actual computational difficulty needed to run a given work unit is the basis for the number of credits that it should be granted. The BOINC system allows for work of any length to be processed and have a user claim identical amounts of credit.

To achieve this BOINC uses benchmarks to measure the speed of a system and in combination with the amount of time it required for a work unit to process can “guess” at the amount of credit it should receive. Since systems have many variables including the amount of RAM, the processor speed, and specific architectures of different motherboards and CPUs, there can be wide discrepancies in the number of credits that different computers believe that each work unit requires to process.

Most projects require a consensus be reached by having multiple hosts return the same work unit. If they all agree then the credit is calculated and all hosts receive the same amount regardless of what they asked for. Each project can use their own policy depending on what they see is best for their specific needs. In general the top and bottom claimed credits are dropped and an average of the remaining is taken.

Total credit

Credits are tracked internally for computers, users, and teams. When a computer processes and returns a work unit it receives no credit. It must first have that work unit validated by the project specific method. Once validated the computer is granted credit, which can be less than, equal to, or greater than what was requested. This amount is immediately added to the computer, user, and team total. If a work unit is returned past the given deadline or is found to be inaccurate it is marked as invalid and the credits granted will be equal to zero. Users and teams commonly determine world rank by comparing the total number of credits accumulated. This highly favors users and teams that have been around for the longest time and makes it extremely difficult for new users to rapidly gain ground even if they are running many computers.

Recent average credit

To calculate the useful amount of work provided by a computer, a special calculation called Recent Average Credit (RAC) is used. This calculation is designed to estimate the number of credits a computer, user, and team will accumulate on an average day. Due to the many variables not taken into account including the inconsistency of host processing, time it takes to validate work units, discrepancies in benchmarks, and possible project down time, the RAC calculation proves to be only a guide.Additionally RAC is independent of computers, users, and teams, meaning they cannot be simply added up. RAC was originally meant to help scientists understand the computational power available to them and to increase competition among users by allowing even new users to quickly move up in rank based on RAC, which should directly reflect how fast work is being processed.

Third party statistics sites

BOINC projects export statistical information in the form of XML files and make it available for anyone to download. Many different third party statistics websites have been developed to track the progress of BOINC projects. The statistics track computers, users, teams, and countries within individual projects and across many projects. Many different sites provide summary graphics, which can be used on web pages that automatically update to contain the statistical information for the specified user or team.

Webpages

*Team Starfire World BOINC Stats 'N Stones — [http://statsnstones.tswb.org Website] by XaaK
*BOINCstats.com — [http://www.boincstats.com Website] by Willy de Zutter
*Boinc.dk — [http://www.boinc.dk/index.php?page=statistics Website] by Janus Kristensen
*BOINC Statistics for the WORLD! — [http://www.boincsynergy.com/stats/index.php Website] by Zain Upton
*Boinc all project stats — [http://www.allprojectstats.com Website] by Markus Tervooren
*BOINC Combined Statistics — [http://boinc.netsoft-online.com Website] by James

External links

* [http://boinc.berkeley.edu/ Berkeley Open Infrastructure for Network Computing (BOINC)]
* [http://boinc-wiki.ath.cx/index.php?title=Main_Page Unofficial BOINC Wiki]