Changes between Version 27 and Version 28 of CreditNew
- Timestamp:
- Mar 25, 2010, 2:59:34 PM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CreditNew
v27 v28 114 114 Notes: 115 115 116 * PFC(J) is not cheat-proof; e.g. cheaters can falsify elapsed time. 116 117 * We use elapsed time instead of actual device time (e.g., CPU time). 117 118 If a job uses a resource inefficiently … … 143 144 and we'll denote it E(J). 144 145 145 ''A posteriori'' estimates of job size may exist also 146 (e.g., an iteration count reported by the app) 147 but this introduces a new cheating risk.146 (''A posteriori'' estimates of job size may exist also, 147 e.g., an iteration count reported by the app, 148 but aren't cheat-proof; we don't use them.) 148 149 149 150 == Cross-version normalization == … … 273 274 == Anonymous platform == 274 275 275 For anonymous platform apps, since we don't reliably276 know anything about the devices involved,276 For anonymous platform apps, 277 since we don't reliably know anything about the devices involved, 277 278 we don't try to estimate PFC. 278 279 279 For each app, we maintain claimed_credit^mean^(A),280 the average of claimed_credit(J)/E(J).280 For each app, we maintain min_avg_pfc(A), 281 the average PFC for the most efficient version of A. 281 282 282 283 The claimed credit for anonymous platform jobs is … … 286 287 The server maintains host_app_version records for anonymous platform, 287 288 and it keeps track of elapsed time statistics there. 288 These have app_version_id = - 1 for CPU, -2 for NVIDIA GPU, -3for ATI.289 These have app_version_id = -2 for CPU, -3 for NVIDIA GPU, -4 for ATI. 289 290 290 291 == Replication ==