Changes between Version 1 and Version 2 of CreditGeneralized

Timestamp:

Aug 8, 2014, 10:34:35 PM (10 years ago)

Author:

davea

Comment:

--

CreditGeneralized

@@ -8 +8 @@
 The current credit system is based on FLOPs:
 a 1 GFLOPS computer running BOINC all the time gets 200 credits per day.
-We did things this way because BOINC was designed to support
-scientific computing, where most apps are floating-point intensive
+We did things this way because BOINC was designed to support scientific computing,
+where most apps are floating-point intensive
 and FLOPS is the standard unit of performance
 (for example, supercomputer performance is measured in FLOPS).
@@ -32 +32 @@
 Depending on the device, this gives an answer in the range of 1,000 to 10,000 FLOPs per hash.
 
-BU did more or less these things, which are completely reasonable.
+BU did these things, which are completely reasonable.
 But it turns out - because ASICs are so fast -
 that BU is granting huge amounts of credit.
-With less than 1,000 users, BU is granting more credit than the 300,000 users of all other projects combined.
+With fewer than 1,000 users, BU is granting more credit than the 300,000 users of all other projects combined.
 
 This situation has 2 undesirable consequences:
@@ -60 +60 @@
 In particular, I propose 4 types:
 
- * Computing credit: general-purpose FLOPs, i.e. what we have now.
- * Disk storage, measured in byte/seconds.
- * Network throughput, measured in bytes, the sum of upload and download.
- * Project-specific credit.
+ * '''Computing credit''': general-purpose FLOPs, i.e. what we have now.
+ * '''Storage credit''', measured in byte/seconds.
+ * '''Network credit''', measured in bytes, the sum of upload and download.
+ * '''Project-specific credit'''.
    Projects can define and grant this however they like.
    For BU, this would be hashes.
@@ -69 +69 @@
    a human activity like annotating video.
 
-The BOINC database would maintain each of these types of credit
+The BOINC database will maintain each of these types of credit
 for each host, user, and team.
-It would store both total and recent average for each type.
+It will store both total and recent average for each type.
 
-The new types of credit would be included in
+Wherever we show credit on project web sites -
+leader boards, user and team pages, etc. -
+we'll show one or more credit types;
+this will be configurable by the project.
+
+The new types of credit will be included in
 the XML statistics files exported by projects.
-Statistics sites (such as BOINCStats) could be extended to
+Statistics sites (such as BOINCStats) will be extended to
 show the new types of credit.