| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: GPU Support Forum
Thread: Run time credit |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 13
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Just don't. You already told us your opine on the matter, and as the situation is, the My Grid / Team / Global stats pages always have referred to computing contributions as runtime... to add that WCG is anyway the only one keeping track of time as a measure of contribution. "Elapsed" is a fair representation and should members work their app_info and other settings to split a card to do multiple jobs... that's perfectly fine, to me [which obviously is not to all].
----------------------------------------[Edit 1 times, last edit by Former Member at Jul 18, 2012 8:24:49 PM] |
||
|
|
Coleslaw
Veteran Cruncher USA Joined: Mar 29, 2007 Post Count: 1343 Status: Offline Project Badges: 
|
The website continues to only report cpu time on the result status page. However, the BOINC database stores both cpu time and elapsed time (i.e. wall clock time between starting the task and ending the task). For GPU tasks, you will be given the 'elapsed time' in your daily history and total stats. CPU tasks will continue to be awarded 'cpu time' in your daily history and total stats. So, does WCG have a way to detect if the work unit was suspended due to a laptop lid being closed? This typically pauses work (unless the power settings and lid close action have been changed in Windows) while the elapsed time (wall clock) typically continues to tick away. I haven't tried this since I don't have a laptop with a GPU for WCG BETA's. Perhaps the techs could test this and chime in? Obviously, the only advantage to doing this is to upgrade a BETA badge and would be highly discouraged.     |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
If a system is in stasis, the elapsed time stops too, at least here it does, both for hibernation and standby. But, it's really irrelevant to CPU based sciences... CPU time is exclusively counted. The only apps that consider the elapsed time is HCC-GPU [in slow boat to China beta]. Anyone closing lid on that ;?
|
||
|
|
|