Really enjoying the Engine COMP so far.
Would it be possible to assign TouchEngine to a specific GPU from within the Engine COMP, in a future release? This would make my Multi-GPU systems very, very happy. Cheers.
Really enjoying the Engine COMP so far.
Would it be possible to assign TouchEngine to a specific GPU from within the Engine COMP, in a future release? This would make my Multi-GPU systems very, very happy. Cheers.
+1
including a way to open a perform window from within the engine COMP
+1 - would also love to be able to assign a task to a GPU
+1 I think Engine COMP is going to really shape how projects are made and pushing it as the main way of organizing large projects (through process management and GPU assignment) is going to be a whole new world.
This would be great for sure. However it makes me curious - how would TOP input / output work in this case? These data would have to be transferred between GPUs. Wouldn’t that introduce big overhead? I thought that for the time being TOP I/O is being handled internally through spout (please correct me if I’m wrong). However with spout it won’t be possible to transfer textures between GPUs, right?
@monty_python it’s hard to say with older GPUs, but certainly with the newer class of Nvidia hardware there are some very interesting changes. NVLink, for example, essentially allows one GPU to write to and read from the memory of another NVLink connected GPU. This skips over the PCIe bus in favor of direct GPU to GPU communication.
Aha, I see, thanks for info. I haven’t thought of NVLink in this case. That might be a way to go.
+1 This would be a great help in many scenarios
Anyone tried this? Does spout allow cross-GPU via NVLink automagically by any chance?
And I presume NVLink, like most Nvidia tech, really wants two exact matching GPUs? The gold standard would be one or more high power GeForce GPUs and one quadro for presentation.