However, it seems that work units from GPU slots 10,11, and 12 are being run on GPU 1 (in addition to the work unit already attempting to run on slot 1)
This essentially means that four work units are attempting to run on GPU1 and nothing is actually getting done on that GPU.
This is what my Folding Slots section of config.xml looked like initially:
Code: Select all
<slot id='0' type='GPU'/>
<slot id='1' type='GPU'/>
<slot id='2' type='GPU'/>
<slot id='3' type='GPU'/>
<slot id='4' type='GPU'/>
<slot id='5' type='GPU'/>
<slot id='6' type='GPU'/>
<slot id='7' type='GPU'/>
<slot id='8' type='GPU'/>
<slot id='9' type='GPU'/>
<slot id='10' type='GPU'/>
<slot id='11' type='GPU'/>
<slot id='12' type='GPU'/>
Code: Select all
<slot id='0' type='GPU'>
<gpu-index v='0'/>
<opencl-index v='0'/>
<cuda-index v='0'/>
</slot>
<slot id='1' type='GPU'>
<gpu-index v='1'/>
<opencl-index v='1'/>
<cuda-index v='1'/>
</slot>
...
<slot id='12' type='GPU'>
<gpu-index v='12'/>
<opencl-index v='12'/>
<cuda-index v='12'/>
</slot>
Right now I've removed slots 10-12 from config.xml in order to get slot 1 back in action, but I still have 3 GPUs just sitting around doing nothing other than looking pretty.
Is this a bug?
Have I messed something up in config.xml?
Any advice would be greatly appreciated.
I've tested this on Linux (Ubuntu Server 18.04 LTS) primarily.
However, Windows 10 Pro (Build 17134) has similar issues.
Windows was worse by far as the automatic gpu-index wasn't always in sequence with the slot id, and so, without specifying a gpu-index it was hard to tell what WU was running on what GPU.
