We currently have a server setup with 2 cpu for our prod enviroment.
We now look at virtual server setup with
2 sockets and 32 virtual processors.
Drives: E, F
Don't forget to add pool "" to your scratchdisk entries.
Your quantity of logical nodes does not need to match the quantity of physical CPUs (or virtual CPUs).
You could have your node.apt file with 8, 16, 32, etc... entries, not just 2.
Performance would take a hit the higher you go, but you COULD do it.
You have to balance degrees of parallelism (your 2 nodes) multiplied by the quantity of concurrent jobs, factoring in the complexity of the jobs, in order to get a sense of how much you will stress your itty bitty PROD box.
Remember that your virtual box sounds bigger than your physical, you may have to see how that affects your licensing.
I would argue that, in a Development environment, you only ever need a one-node and a two-node configuration file. The only exception is where you need to develop with node pools. If a job runs on two nodes, it will run on 2000.
Virtual server makes no difference.
Switching to a cluster or grid topology would make a difference.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.