I'm trying to do a script so that I can run
seti on one GPU

and

GPUGrid on another.

is there a list of application names at all?

there are
acemd and acemdlong
are there any others?

BOINC can do this for you without any special script. Use "exclude_gpu" option in the cc_config.xml file, such as below:

<cc_config>
<options>
<report_results_immediately>1</report_results_immediately>
<use_all_gpus>1</use_all_gpus>


<!-- ======= SETUP GPU 0: (Use GPUGrid, not SETI) ======= -->
<exclude_gpu>
<url>http://setiathome.berkeley.edu/</url>
<device_num>0</device_num>
</exclude_gpu>


<!-- ======= SETUP GPU 1: (Use SETI, not GPUGrid) ======= -->
<exclude_gpu>
<url>http://www.gpugrid.net/</url>
<device_num>1</device_num>
</exclude_gpu>

</options>
</cc_config>


You can add as many exclusions as you want. Any project you've set options to get CUDA work will process on GPU0 except for SETI, and likewise for GPU1 except for GPUGrid. So, let's assume you also don't want Primegrid to run on GPU0 (dedicated just for GPUGrid) -- then you just use the same format but put in PrimeGrid's URL.

BOINC can do this for you without any special script. Use "exclude_gpu" option in the cc_config.xml file, such as below:

<cc_config>
<options>
<report_results_immediately>1</report_results_immediately>
<use_all_gpus>1</use_all_gpus>


<!-- ======= SETUP GPU 0: (Use GPUGrid, not SETI) ======= -->
<exclude_gpu>
<url>http://setiathome.berkeley.edu/</url>
<device_num>0</device_num>
</exclude_gpu>


<!-- ======= SETUP GPU 1: (Use SETI, not GPUGrid) ======= -->
<exclude_gpu>
<url>http://www.gpugrid.net/</url>
<device_num>1</device_num>
</exclude_gpu>

</options>
</cc_config>


You can add as many exclusions as you want. Any project you've set options to get CUDA work will process on GPU0 except for SETI, and likewise for GPU1 except for GPUGrid. So, let's assume you also don't want Primegrid to run on GPU0 (dedicated just for GPUGrid) -- then you just use the same format but put in PrimeGrid's URL.

Thanks. I did mean trying to write a config file.

so far I had this
<cc_config>
<options>
<report_results_immediately>1</report_results_immediately>
<use_all_gpus>1</use_all_gpus>


<exclude_gpu>
<url>http://www.gpugrid.net/</url>
<device_num>0</device_num>
<type>nvidia</type>
<app>acemd</app>
<app>acemdlong</app>
</exclude_gpu>

</options>
</cc_config>


that worked at first, but then when the original Seti tasks finished, it
loaded GPUGrid onto that GPU.

that worked at first, but then when the original Seti tasks finished, it
loaded GPUGrid onto that GPU.

From your computers page, it shows you using BOINC 6.10.58.


The BOINC Client Configuration page shows you must be running BOINC client 6.13 or higher to use the "exclude_gpu" option.


That's probably why it is not working for you. Try downloading BOINC 7.0.28 with the same cc_config.xml. Also, make sure you load the preferences in BOINC, forcing the client to read the information in the cc_config.xml file. If successful, you should be able to see the event log showing the exclusion.

It's not for me, it's for someone in my team and he is running
the latest version - 7.0.28

If they are both the same type (ATI or Nvidia) then you don't need to specify <type>. You also don't need the <app>. Both are optional. I use the following on mine:

<cc_config>
    <options>
        <http_1_0>1</http_1_0>
	<http_transfer_timeout>120</http_transfer_timeout>
        <exclude_gpu>
            <url>http://climateprediction.net</url>
        </exclude_gpu>
        <exclude_gpu>
            <url>http://einstein.phys.uwm.edu</url>
        </exclude_gpu>
    </options>
    <log_flags>
        <sched_op_debug>1</sched_op_debug>
        <work_fetch_debug>0</work_fetch_debug>
    </log_flags>
</cc_config>

Which says:
1. Use HTTP 1.0.
2. Use a 2 minute timeout on file xfers and scheduler requests (default is 5 mins).
3. Don't use the GPU for Climate Prediction (they don't have a GPU app but it tries asking for Nvidia anyway).
4. Don't use the GPU for Einstein.

If you have an "always on" internet then you don't need the <return_results_immediately> as GPUgrid does it anyway.

---

BOINC blog

Thanks MarkJ,
I'll give that a try.