Changes between Version 2 and Version 3 of CreditProposal

Timestamp:

Jan 9, 2008, 2:38:04 PM (16 years ago)

Author:

Nicolas

Comment:

m

CreditProposal

@@ -16 +16 @@
  * Computation that needs a large amount of RAM.
  * Computation that needs a large amount of storage.
- * Storage (e.g. GB/day)
- * Storage, with network bandwidth and/or availability requirements
- * Network bandwidth (e.g. web crawling)
- * Network bandwidth at particular times of day (e.g. Internet performance study)
- * Deployment on a wide range of computer types (e.g. studies of computer usage)
- * Computation with human "steering"
- * Human activity (e.g. Stardust@home-type projects)
+ * Storage (e.g. GB/day).
+ * Storage, with network bandwidth and/or availability requirements.
+ * Network bandwidth (e.g. web crawling).
+ * Network bandwidth at particular times of day (e.g. Internet performance study).
+ * Deployment on a wide range of computer types (e.g. studies of computer usage).
+ * Computation with human "steering".
+ * Human activity (e.g. Stardust@home-type projects).
 
 == Proposal ==
@@ -39 +39 @@
 == Examples ==
 
- * Computational projects would have to derive a credit function based on how fast various types of computers run their applications (and how much they value each application).  We can supply automated tools for this.
+ * Computational projects would have to derive a credit function based on how fast various types of computers run their applications (and how much they value each application). We can supply automated tools for this.
  * Suppose a project's application needs at least 16 GB RAM.  Its credit function would be zero for hosts with < 16 GB RAM.  Its value for hosts with at least 16 GB would be limited by the normalization rule.
  * For a storage-only projects, C(H) would be proportional to available disk space (possibly with some additional consideration for network bandwidth etc.).