In ap_cmdline_win_x86_SSE2_OpenCL_Intel.txt: -cpu_lock -instances_per_device 1
in ap_cmdline_win_x86_SSE2_OpenCL_NV.txt: -cpu_lock -instances_per_device 3

The same result in Task-Manager:
1 Intel iGPU app at Core#0
1 NV GPU app at Core#0 and 1 NV GPU app at Core#1

I think Raistmer means -instances_per_device 3 for both apps

You can just set (for both apps) -instances_per_device 8
-instances_per_device don't control how many apps (.EXEs) are started
It only tells the already started apps (started by BOINC, or by (several) benchmark tests) to really 'work' (use the GPU to compute and not wait for it to become free)

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

In ap_cmdline_win_x86_SSE2_OpenCL_Intel.txt: -cpu_lock -instances_per_device 1
in ap_cmdline_win_x86_SSE2_OpenCL_NV.txt: -cpu_lock -instances_per_device 3

The same result in Task-Manager:
1 Intel iGPU app at Core#0
1 NV GPU app at Core#0 and 1 NV GPU app at Core#1

You could try -cpu_lock_fixed_cpu 3 (or 4) for the Intel iGPU. That should work for now.

I expect Raistmer may modify the mutex implementation to make some future versions cooperate between different brand GPUs, but no promises...

                                                                   Joe

There will be special command-line option to handle such cases in new builds:

-total_GPU_instances_num N : To use together with -cpu_lock on multi-vendor GPU hosts. Set N to total number of simultaneously running GPU
	OpenCL SETI apps for host (total among all used GPU of all vendors). App needs to know this number to properly select logical CPU for execution
	in affinity-management (-cpu_lock) mode.

mutexes remain unchanged but their usage decoupled from affinity management with this new option. Can be used on multi-vendor hosts w/o messing up GPUlock feature.