| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 9
|
|
| Author |
|
|
Mumak
Senior Cruncher Joined: Dec 7, 2012 Post Count: 477 Status: Offline Project Badges:
|
I was wondering why my GPU WUs take longer time than before, then I found it.
----------------------------------------I installed latest beta client v7.0.52 and BOINC 7.0.45 and later according to change log applies the CPU throttling % to GPUs now too! Since I had this set to 80% the GPU was not fully utilized. It would be nice if the CPU and GPU utilization was separated in the client though. ![]() |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The understanding is that currently that throttling can *not* be separated. Technically, the GPU task throttling is done by throttling the CPU which for BOINC has always been general, all jobs, and not at a single thread level.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
P.S. If you do CPU throttling because of heat issue, have a look at TThrottle that longer has had capability to throttle CPU and GPU [heat control]. The BOINC version is not exactly the best... if set at 80%, it means running 4 seconds, pausing 1 second.
If you do CPU throttling because of wanting to have some CPU time reserved for the user... refer to previous para... it's useless in that department, since 4 seconds BOINC runs 100% and then 1 second your CPU/GPU idles... The one and only object of the BOINC CPU time% control was to manage/prevent overheating in laptops! Desktops rarely have the issue [if kept dustbunny free] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
P.P.S. The BOINC throttle default for WCG is now 50% [was 60%], meaning tasks would run 1 second, pause 1 second. This is to prevent/minimize chance of what's called thermal and mechanical stress... for instance the fans constantly stopping and starting greatly shortening their life expectancy.
|
||
|
|
Mumak
Senior Cruncher Joined: Dec 7, 2012 Post Count: 477 Status: Offline Project Badges:
|
I had 80% set from the past and didn't take any CPU tasks on that machine, so I didn't care about that setting.
----------------------------------------I just wanted to make users aware that this new "feature" affects their GPUs now. ![]() [Edit 1 times, last edit by Mumak at Feb 15, 2013 8:29:42 PM] |
||
|
|
jay_Orlando
Senior Cruncher USA Joined: Jan 4, 2006 Post Count: 189 Status: Offline Project Badges:
|
Rob,
----------------------------------------50% throttling? Wouldn't that stress out the CPU or floating point unit: Starting and then stopping or idling every second? since they are small, wouldn't the delta of Heat/physical_area be greater? I thought throttling was not specific to a project - but rather a BOINC preference. I'm admitting a lot of confusion today.. :-) Jay ![]() |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The reverse, as explained, at 1 second the CPU cant go to the full operating heat level, so the cool down will be less and since that is only one second, the delta will be smaller, to the point that the fan does not even have to kick in, preventing mechanical stress at that. BOINC internal method is a dog of a throttling system, not promoted by anyone, used for lack of any general, all platform better tool/method. BTW, WCG[speak IBM] does know what it's about ;>), which is why they reduced the 60% default [run 3 seconds, pause 2 seconds] to 50%. :D
Personally, if on Windows, I'd recommend anything-but the BOINC throttle... TThrottle, ThreadMasterGUI [TMG], Process Lasso to name a few do a better job. TThrottle did/does not do a good job on my hyperthreaded octo though, so there I use ThreadMasterGUI during the summer season [Works for me through W8], limiting processes to 80% or thereabouts. That tool allowed throttling at the science level... one runs the CPU/FPU hotter than the other. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The one and only object of the BOINC CPU time% control was to manage/prevent overheating in laptops! Desktops rarely have the issue [if kept dustbunny free] I'd add "at least not if ambient (room) temperatures are kept below 80F/27C".It is picky (maybe even irksome - if so, I apologize in advance!) of me to mention the ambient temp, but running 30+ cores and GPUs of science provides a superb auxiliary heat source for an entire floor in my home during the winter. EFMER's BoincTasks and TThrottle are my "insurance policy" during the summer...having had, on occasion, power "brownouts" and brief interruptions which would cause my air conditioning to trip out while my UPS systems would keep my computers up, resulting in a rapid increase (on the order of 0.5 degrees/minute ) in ambient temperatures.Depending upon where in the world you live, ambient temperatures can be an issue even for a single system crunching science...TThrottle is nice insurance. Especially if you build your own systems as I do, and so always have that question "Did I get the thermal paste applied properly?" nagging at the back of your mind. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Personally, if on Windows, I'd recommend anything-but the BOINC throttle... TThrottle, ThreadMasterGUI [TMG], Process Lasso to name a few do a better job. <emphasis mine> Any counterpart recommendations for Linux/Ubuntu?; ; andzgridPost#954 ; [Edit 1 times, last edit by Former Member at Feb 25, 2013 3:59:51 PM] |
||
|
|
|