Multiple GPU concurrency control

[MindCrime]

I've got a machine with a 7970 and iGPU. I want to run SETI on both, but I want to run 2x on the 7970 and only 1x on the iGPU.

I did have <app_config... <gpu_usage>0.5, for a bit but it runs 2x on all GPUs and that consumes a lot of CPU on the iGPU.

So can anyone help me setup to run 2x on the 7970 and 1x on the iGPU? I feel like this is gonna require an app_info file.

I can think of only 3 projects this could happen on; Collatz, Einstein, and SETI since they support pretty much all GPUs.

[Bryan]

That is the kind of thing Emsti did the multiple BOINC instances to handle: HERE (http://www.setiusa.us/showthread.php?6595-Running-2-clients-on-the-same-machine-without-VM&highlight=running)

Very simple to setup and each runs independently.

[FourOh]

I prefer to set it up in app_config:

<app_config>
<app>
<name>setiathome_v8</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>0.1</cpu_usage>
</gpu_versions>
</app>

<app>
<name>astropulse_v7</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>0.1</cpu_usage>
</gpu_versions>
</app>

<app_version>
<app_name>setiathome_v8</app_name>
<plan_class>opencl_intel_gpu_sah</plan_class>
<ngpus>1</ngpus>
</app_version>

<app_version>
<app_name>astropulse_v7</app_name>
<plan_class>opencl_intel_gpu_102</plan_class>
<ngpus>1</ngpus>
</app_version>
</app_config>

[MindCrime]

ahh so the <plan_class> is the key, I got an answer on the seti forums using an app_info setup, I like yours better. I hope I can remember to check back here when I'm running SETI again, think I'm done for a while.