The only pro I can think of would be to reduce GPU use to keep temperature or power use down, but that would be better implemented as GPU throttling.
On Thu, Jul 4, 2013 at 5:52 AM, Bernd Machenschalk <bernd.machensch...@aei.mpg.de> wrote: > On 04.07.13 13:15, Heinz-Bernd Eggenstein wrote: > >> I guess there are several pros and cons, e.g.: >> >> cons: >> - one one hand, GPU apps (depending on the CPU share?) get a higher OS >> prio (in terms of "niceness") to prevent the GPU being starved. Throttling >> the CPU might very well cause this starvation >> - if a GPU app has a rather low CPU runtime share in the first place, >> further CPU throttling does not seem too useful. >> - in order to avoid GPU load to interfere with the user doing non-BOINC >> related stuff, there is already the setting "Suspend GPU work while >> computer is in use". > > > Here's one more: > > When not synchronized with GPU-CPU communication (kernel launches, data > transfer) throtteling an App can break any running GPU task. I'm not sure > whether the throtteling implementations of all BOINC Clients that are being > used properly honor critical sections, nor am I that all GPU apps of all > projects make proper use of these. > > >> pros: >> I can't think about many > > > Actually I can't think about any. > > Best, > Bernd > > > _______________________________________________ > boinc_dev mailing list > boinc_dev@ssl.berkeley.edu > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
