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.
I seem to remember someone (me) suggesting a more generic means of scheduling resources. Anyone have a grad student that wants to rewrite the scheduler as a masters project? Eric _______________________________________________ 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.
