Changes between Version 4 and Version 5 of CreditGeneralized

Timestamp:

Aug 11, 2014, 4:52:14 PM (10 years ago)

Author:

davea

Comment:

--

CreditGeneralized

@@ -23 +23 @@
 It can be done on CPUs and GPUs, but it can be done much faster on ASICs.
 These ASICs can only do hashing; they can't do floating-point math,
-and they can't be used by any BOINC project other than BU.
+and they're of no use to any BOINC project other than BU.
 
 The question was: how should BU grant credit for its jobs?
@@ -42 +42 @@
    no longer measures its peak performance in FLOPS.
  * The competitive balance between volunteers is lost.
-   The top users and teams (BOINC-wide) will be only those with ASICs.
+   The top users and teams (BOINC-wide) will be only those with ASICs running BU.
  * The competitive balance between projects is lost.
    BU will always grant far more credit than other projects,
@@ -63 +63 @@
 
  * '''Computing credit''': general-purpose FLOPs, i.e. what we have now.
- * '''Storage credit''', measured in byte/seconds.
+ * '''Storage credit''', measured in byte/seconds (possibly multiplied by availability).
  * '''Network credit''', measured in bytes, the sum of upload and download.
  * '''Project-specific credit'''.
@@ -78 +78 @@
 leader boards, user and team pages, etc. -
 we'll show one or more credit types;
-this will be configurable by the project.
+the choice of types will be configurable by the project.
 
 The new types of credit will be included in
@@ -86 +86 @@
 
 == Discussion ==
+
+=== Are these 4 types enough? ===
+
+I'd prefer to use only these 4 types,
+rather than e.g. having an extensible system where projects can add several
+of their own types.
+Reasons: conceptual simplicity, and also ease and efficiency of implementation
+(add fields to existing DB tables rather than create new/big tables).
+
+=== Other app-specific coprocessors ===
 
 Eric pointed out the possibility of a variant of the SETI@home app