The time has come when PrimeGrid is going to release a second CUDA app. This brings us into quite an unfortunate situation: we need app filtering extended to allow selection of different application sets for GPU and CPU, because users want to run different apps for CPU and GPU, because some are more efficient on their machines than others, and also, because of badges that are per-app in PrimeGrid.
With one GPU app is possible to "cheat" BOINC: select only CPU apps that you want to run and also enable sending work from other projects if there is none for selected ones. In this case there will never be work for GPU, so it will pick up one available app. With multiple GPU apps this is no longer possible because work might be sent from any of the GPU apps, whereas the user might only want work from a single one. The scheduler now understands <app_id>N</app_id> as a preferred app. Would it be possible to extend scheduler to also understand <cuda_app_id>N</cuda_app_id> and <ati_app_id>N</ati_app_id>, with GPU fallback to CPU app filtering (<app_id>N</app_id>) if no ati_ or cuda_ versions are selected? -- Pagarbiai / Sincerely Rytis Slatkevičius +370 670 77777 _______________________________________________ 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.
