Yeah - Vmotion may work with lightly loaded systems - it may never complete with heavy memory IO in progress though.
There's also size limits on the vmware guests - such as processor core limits of 2 or 4 now, and limitations in the implementation of the processor scheduling. + you can't scale up vmware machines as well as you can the larger hardware systems.
So vmotion may be useful in moving the lightly loaded guest systems OFF the server itself, to give more capacity to an instance - but would impose maximum size limits of its own - in both CPU and memory terms.
Implementing an ability to share and migrate workloads at the application level might be an alternative move - that way you could perhaps distribute workload live to some grunty boxes with plenty of spare CPU cores and memory capacity (considering how cheap 128GB 24 CPU core systems are now....) -
Using such a method you could also distribute workload over more vmware guests - but then you're "wasting" memory and cpu workload on OS instances rather than game workload:-)
Slashdot Mirror
Yeah - Vmotion may work with lightly loaded systems - it may never complete with heavy memory IO in progress though.
There's also size limits on the vmware guests - such as processor core limits of 2 or 4 now, and limitations in the implementation of the processor scheduling.
+ you can't scale up vmware machines as well as you can the larger hardware systems.
So vmotion may be useful in moving the lightly loaded guest systems OFF the server itself, to give more capacity to an instance - but would impose maximum size limits
of its own - in both CPU and memory terms.
Implementing an ability to share and migrate workloads at the application level might be an alternative move - that way you could perhaps distribute workload live to some grunty boxes with plenty of spare CPU cores and memory capacity (considering how cheap 128GB 24 CPU core systems are now....) -
Using such a method you could also distribute workload over more vmware guests - but then you're "wasting" memory and cpu workload on OS instances rather than game workload :-)