Thank you. That will be popular, and will resolve much confusion on the boards. May I suggest that you at least break it down to the primary (co-)processors recognised by BOINC: "no CPU", "no nVidia GPU", "no ATI GPU". At the project level, users may wish to, for example, dedicate an ATI GPU to Milkyway and dedicate a nVidia GPU to Collatz.
--- On Sat, 26/9/09, David Anderson <[email protected]> wrote: From: David Anderson <[email protected]> Subject: Re: [boinc_dev] Why did BOINC contact Prime Grid, and Why did it DL execuatables To: "Richard Haselgrove" <[email protected]> Cc: [email protected] Date: Saturday, 26 September, 2009, 9:43 PM I agree. I'll do this soon (just the "no CPU" and "no GPU" prefs for now). -- David Richard Haselgrove wrote: > Following on from my previous thought, it seems that we aren't paying enough > attention to the scope of some of these settings. > > An XML entity has two different scopes: > > a scope for the DEFINITION > a scope for the VALUE > > Many BOINC preferences are global for both definition and value. They tend to > be stored in prefs.xml (global or override). > > Other preferences are project-specific for both definition and value, like > the screen-saver controls Nicolas reminded us of . They live in account.xml > and client_state.xml. > > But there's a third class, with a global definition scope but a project value > scope, which seems to me to be under-utilised. In fact, it has only one > member: resource share. > > I propose that we examine the recent resource additions, and consider whether > more of them should be moved into the middle scope (global def, project > value). Use/don't use CPU/GPU is an obvious place to start, but others might > be considered: suspend (CPU/GPU) while in use might be another candidate - > different project apps interfere with the desktop to different degrees, and I > might be willing to let GPUGrid, for example, run a CUDA app while I'm > active, but not willing to run an AQUA CUDA app. > > _______________________________________________ > boinc_dev mailing list > [email protected] > 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 [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
