daxtrajero wrote:
So if I have a Win32 database application as I mention I have 3 scenarios
1. Non virtualized setup - 1x Win2k3 server and 10 Windows workstations that connect to it over the LAN. Troublesome as 100Mbps LAN is the bottleneck
2. Virtualizaed setup - 1x virtual 2k3 server, 10 virtual Windows workstations configured to connect to it. Each user RDP's into their respective virtual PC
What are the performance benefits to option 2 ?
option # 2 is better because assuming that both the w2k3 server and the windows workstations are virtualized, then communication between the workstations and server is faster than the 100MB links you have in physical network.
The w2k3 server can also be a terminal server - if that is the case, then your users rdp to the term sessions, in order to talk to the server/db that is also running (I presume) on the w2k3 server. So, think I see these possible scenarios:
1)physical windows term server, also running db - users rdp to term sessions to run application. (better than having application client on physical workstation, because it bypasses slow lan)
2)virtual windows term server - also running db - users rdp to term sessions (see above)
3)virtual windows db server - users use virtual windows desktops and either the view client or direct RDP (better than having application client on physical workstation, because it bypasses slow lan)
4)virtual windows term server - also running db - and either using native rdp or installing view and having it broker the term sessions, so that users connect to term desktops via the view client)