One point of generic resource allocation is that the resource definitions aren't in the source code, but are defined in XML. Requiring per app and per project server source customization is a problem, not a solution.
On Sat, Dec 19, 2009 at 10:59 AM, David Anderson <[email protected]> wrote: > Eric J Korpela wrote: >> >> This is part of the problem we face because we didn't treat resources >> in a generic manner in the scheduler. The ATI astropulse application >> only uses the GPU for parts of the application, and there's no means >> in the scheduler to deal with an application that uses 85% of a CPU >> and 10% of a GPU. Other than changing the scheduler code every time >> we release an new version of this app, that is. > > That's what sched_customize.cpp is for. > It explicitly supports apps that use x% of a CPU and y% of a GPU. > There's no point in trying to define a "generic" model; > the next app to come along will break the model. > _______________________________________________ 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.
