RTC Application Move from a Physical server to a VM
One answer
2.40/2.93 = .81 (+ the VM difference)
and 1/2 the processors so if there was waiting before, you will wait more or thread switch more.. so a small increase in overhead.
and I would be wary of putting reporting on the same server as the RTC app.. reporting is CPU heavy.
I assume the DB is on another machine.
Comments
Sam,
RRDI/Cognos, I wasn't worried about memory.. worried about processor availability for RTC app. we had a shared VM machine and constantly had perf problems cause the other VM's had higher proprity, and other apps spiked performance when we needed 100% for RTC. so sharing is not a favored approach for me.
I can't help on any specific config changes to mitigate the impacts as they are really physical in nature.. slower processor and system sharing on a virtual environment. (you can't go slower and make it up in volume!)
yes, sadly RTC does not support the std application model where u can spin up another engine and load balance work over one database.. Each new instance is a separate unique database. I haven't seen any real plan to change the design (it would solve and incredible number of operational, deployment and scalability problems)