Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I was wondering is there a good rule of thumb around configuring virtual CPUs and memory for a Windows 2008 Server R2 Remote Desktop Services host running within a VMware VM?

Our infrastructure team has suggested that two vCPUs (2x2.4 GHz AMD Opteron) and 8GB vRAM be presented to the guest for four concurrent developers running Visual Studio 2010, each with their own SQL Server 2008 R2 Developer instance on the guest, plus a couple sites per developer to use in IIS on the guest.

I was thinking that we'd want something more along the lines of having one vCPU per developer, and about three to four gigs of vRAM per developer. So, I would have expected more along the lines of 4 vCPUs and 12-16 GB vRAM.

I'd really appreciate a second opinion.

While researching, I did run across this article here, but it was more geared toward provisioning storage. In our case storage isn't really an issue as it is backed by our Clarion SAN which we have no control over, really.

share|improve this question
up vote 1 down vote accepted

I'd recommend going with the smaller vCPU allocation to start. The VMWare host will have a harder time scheduling a 4 vCPU guest, so it's best to start small and add as needed. I'd stick with your infrastructure team's recommendation of 2 vCPU and 8GB RAM.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.