Hi Carsten,
I never tried it (perhaps will) - but even if there is a way to run more than one instance of Resolve, the heavy dependence of the efficiency of each instance on the GPU subsystem makes simultaneous export of more than a single file a rather sub-optimal way to take advantage of the 2990WX'es plethora of cores/threads, I'm afraid...
On the other hand, the beauty of my usage scenario is that
one of the number-crunching applications (Moldflow CAE system in this case) doesn't use the graphics subsystem at all, so it can be owned and managed by Resolve in the usual way - without any extra overhead or dividing the graphical subsystem in two parts - one for Resolve, the other for Moldflow... I've been working like this ever since I finished building my Threadripper workstation, and had zero problems with it! Yes - it's true that in the earlier years, Moldfllow's solvers not only scaled across the CPU's threads, but could also use CUDA cores of an nVidia, or OpenCL in the case of an AMD GPU card. But this has never been properly implemented, and so the nVidia Fermi architecture was the last one used by Moldflow for this type of CPU/GPU parallelization. BTW it never worked really well, so I'm glad Moldflow developers dropped GPU acceleration altogether.
In fact, what I do is setting up my Moldflow projects on an average laptop (the same one I would take with me to my Moldflow clients);
I am accessing the laptop and the Moldflow GUI (pre- and post-processor for the FEM model and analysis results)
from my main 2990WX workstation using Remote Desktop. After my FEM model is ready, I'll simply launch the solver on the workstation rather than the slowish laptop; for as long as the analysis lasts I can then minimize my Remote Desktop and with the Moldflow analysis running in the background, I start my usual interactive Resolve session... Works like a charm - but of course, I'd like to squeeze every little bit of computing power out of such a setup
That said, of course I do not always work like this; facing a complicated Moldflow problem with the part and mold models several million 3D elements each, I will never share my WS resources (and my own cramped CPU I have in my head
) with anything else, not even mention Resolve. And vice-versa: when working on sub-frame A/V sync of a multicamera music video, I'll need each and every CPU and GPU core to do it properly in Resolve (not to mention RAM, of which only having 64GB I couldn't possibly accommodate two big projects in memory without disk trashing. Another example of my Resolve pursuits which I'd never even try to conduct with a Moldflow analysis running in the background is any project involving Fusion....But with all light-weight projects of both CAE and NLE nature, this is the way I'm tackling the 2990WX architectural quirks and sometimes unforeseeable behavior... Sometimes I'd even run more than one Moldflow analyses in the background, if for instance all I need to do in Resolve is some media management, timeline housekeeping and introductory cutting!
Piotr
AMD TR 2990WX CPU | MSI X399 CARBON AC | 64GB RAM@XMP3200 | 2x RTX 2080Ti GPU | 4x 3TB WD Black RAID0 media drive | 3x 1TB NVMe RAID0 cache drive | SSD SATA system drive | AX1600i PSU | Decklink 12G Extreme | Samsung UHD reference monitor (calibrated)