Changes between Version 2 and Version 3 of CreditProposal
- Timestamp:
- Jan 9, 2008, 2:38:04 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CreditProposal
v2 v3 16 16 * Computation that needs a large amount of RAM. 17 17 * Computation that needs a large amount of storage. 18 * Storage (e.g. GB/day) 19 * Storage, with network bandwidth and/or availability requirements 20 * Network bandwidth (e.g. web crawling) 21 * Network bandwidth at particular times of day (e.g. Internet performance study) 22 * Deployment on a wide range of computer types (e.g. studies of computer usage) 23 * Computation with human "steering" 24 * Human activity (e.g. Stardust@home-type projects) 18 * Storage (e.g. GB/day). 19 * Storage, with network bandwidth and/or availability requirements. 20 * Network bandwidth (e.g. web crawling). 21 * Network bandwidth at particular times of day (e.g. Internet performance study). 22 * Deployment on a wide range of computer types (e.g. studies of computer usage). 23 * Computation with human "steering". 24 * Human activity (e.g. Stardust@home-type projects). 25 25 26 26 == Proposal == … … 39 39 == Examples == 40 40 41 * 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). 41 * 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. 42 42 * 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. 43 43 * For a storage-only projects, C(H) would be proportional to available disk space (possibly with some additional consideration for network bandwidth etc.).