| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: GPU Support Forum
Thread: Random GPU question |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 12
|
|
| Author |
|
|
Skivelitis2
Advanced Cruncher USA Joined: Mar 21, 2015 Post Count: 113 Status: Offline Project Badges: 
|
Back when WCG had GPU work, how was runtime calculated? Did it count the same as any other core or was there some type of multiplier involved?
---------------------------------------- |
||
|
|
Aperture_Science_Innovators
Advanced Cruncher United States Joined: Jul 6, 2009 Post Count: 139 Status: Offline Project Badges: 
|
Unless I'm greatly mistaken, it was counted the same as other runtime was--one hour of runtime per hour of CPU time. This meant that if you were running multiple GPU WUs on a single card, you could get >1 hour per hour of wall-clock time--but also at the expense of less pure CPU work.
---------------------------------------- |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
https://secure.worldcommunitygrid.org/help/vi...rchString=GPU+and+Runtime
'Help' is that button near the top of all forum pages that links to wealth of of information on most all you want to know, in concise text form.  |
||
|
|
enels
Senior Cruncher Joined: Apr 25, 2008 Post Count: 286 Status: Offline Project Badges:
|
I don't know that any project in BOINC measures GPU time. And GPU tasks nowadays use significantly less CPU time than GPU time.
|
||
|
|
KLiK
Master Cruncher Croatia Joined: Nov 13, 2006 Post Count: 3108 Status: Offline Project Badges:
|
I don't know that any project in BOINC measures GPU time. And GPU tasks nowadays use significantly less CPU time than GPU time. SETI@home does, example of my WU: http://setiathome.berkeley.edu/workunit.php?wuid=1945990635 Run time is GPU time...& CPU time is less! |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges: 
|
I don't know that any project in BOINC measures GPU time. And GPU tasks nowadays use significantly less CPU time than GPU time. POEM, GPUGrid and SETI just to name a few.
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
  |
||
|
|
enels
Senior Cruncher Joined: Apr 25, 2008 Post Count: 286 Status: Offline Project Badges:
|
I can't find any GPU time recorded per task or in aggregate at the GPUgrid. Only CPU time per task and Run time per task. Obviously GPU time can be less than Run time. As CPU time can.
Back on topic I remember GPU version of HCC required 1 core per task. My 4 core machine ran 3 CPU HCC tasks plus 1 GPU HCC task. That was counted at the WCG as 4 days of runtime per day. Technically it should have been 5 as there where 4 CPU + 1 GPU tasks engaged. HCC used a version of OpenCL that required an entire core for HCC. These days, however, OpenCL and CUDA are more stingy with their CPU usage. |
||
|
|
branjo
Master Cruncher Slovakia Joined: Jun 29, 2012 Post Count: 1892 Status: Offline Project Badges: 
|
Not really. I have run 32 tasks with my octo cpu...
---------------------------------------- Crunching@Home since January 13 2000. Shrubbing@Home since January 5 2006  |
||
|
|
noderaser
Senior Cruncher United States Joined: Jun 6, 2006 Post Count: 297 Status: Offline Project Badges: 
|
I can't find any GPU time recorded per task or in aggregate at the GPUgrid. Only CPU time per task and Run time per task. Obviously GPU time can be less than Run time. As CPU time can. Maybe you should have a look at the link above your first post. How is "run time" calculated? "Run time" is simply a measurement of how long a volunteer's device spends running World Community Grid tasks. You accumulate run time for running tasks on your device's GPU, CPU, or both. If you contribute GPU time, the run time is the actual elapsed time in which the World Community Grid task executes on the GPU. In other words, if the task starts at 10:15am and finishes at 10:19am, you accumulate 4 minutes of run time. If you contribute CPU time, the picture is a bit more complicated because CPUs can prioritize different tasks and have multiple cores. Only the time a CPU spends actually executing a World Community Grid task counts toward your run time. As an example, if a quad-core computer runs a World Community Grid task on each core at 75% throttle from 10:15am to 10:19am, then each core will accumulate 3 minutes of run time (75% of 4 minutes). Across all 4 cores, the total run time would therefore be 4 x 3 minutes = 12 minutes. |
||
|
|
KLiK
Master Cruncher Croatia Joined: Nov 13, 2006 Post Count: 3108 Status: Offline Project Badges:
|
I can't find any GPU time recorded per task or in aggregate at the GPUgrid. Only CPU time per task and Run time per task. Obviously GPU time can be less than Run time. As CPU time can. Back on topic I remember GPU version of HCC required 1 core per task. My 4 core machine ran 3 CPU HCC tasks plus 1 GPU HCC task. That was counted at the WCG as 4 days of runtime per day. Technically it should have been 5 as there where 4 CPU + 1 GPU tasks engaged. HCC used a version of OpenCL that required an entire core for HCC. These days, however, OpenCL and CUDA are more stingy with their CPU usage. Run time is GPU time...unless you're not using GPU, so then you use some R Pi or sthg?! Imagine a run time, as a device time run... also, older apps were written for "single-precision calcs"...so those apps have been using almost a whole CPU for a GPU crunching...  |
||
|
|
|