Wednesday, July 18, 2012

Hardware requirements - Developing for SharePoint 2013

If you are developing on-premise solutions where you deploy good old WSP packages to SharePoint, this is a post for you. If you are developing SharePoint Apps, you can get away with just about any setup (overly simplified statement).

The minimum recommended requirements for SharePoint development just got upped. TechNet recommends a minimum of 8GB ram and 4 cores. This is double of what was recommended for SharePoint 2010. My own tests show that you can perfectly well develop with 2 cores and 8GB ram on a single VM with DC, SQL, SharePoint 2013 and Visual Studio installed….if you have an SSD drive. You can also go down on ram to about 6GB depending on which features you use, but I think 8GB is acceptable.

My dev box is a Lenovo T420s (i5 core) with 2x250GB SSD’s and 16GB ram running VMWare Workstation. Assigning 8GB to the VM even allows a second  VM to spin up for multi-server testing.  This setup yields an experience which is perfectly acceptable and which don’t give me gray hair waiting for everything (something virtual environments at customers give me all the time).
Sum it up:
  • 8GB ram
  • 2 cores
  • SSD (preferably SATA3 like the Samsung 830)
If you are a customer paying consultants developing on their own hardware, use this a checklist, or demand a compile-wait-deploy-discount.

A more ideal setup is a separate DC with 512MB ram (or even less), one SharePoint VM and one for Office Web Apps. Basically, the more physical ram you have, the more VM's you can spin up for different roles.


  1. Hello Mikael!

    Thanks for sharing.

    I'd like to add: I've installed SharePoint Foundation 2013 Preview on virtual machine with only 3Gb RAM, and no SSD, while MSDN decrees 8Gb minimum. I have been playing with SharePoint Designer and SharePoint sites for some time: simple customizations, filling lists with some data (up to few thousand records), etc. So far, all is smooth and fast.

    I realize, that development tools significantly add to requirements, especially Visual Studio, however with Napa available and the new concept of SharePoint Apps it seems not so crucial any more. Also, Publish capability allows us to perform Visual Studio development on the main computer, while running SP2013 inside a virtual machine.

    In sum, I think MS is basically playing safe, and for development purposes, when you don't have much data and concurrent users, I assume you can use the same environment as for SharePoint 2010.

    1. Good comment and I agree. But for me I would not do SP dev without an SSD. It makes dev just that much faster and gives me less grey hair :)

    2. Sure. Visual Studio without SSD is inevitably slow, especially on huge solutions.

  2. Thanks for sharing hardware requirements for share point 2013. Now I need to update my computer to use this amazing platform.

    sharepoint 2010 development

  3. I don't have that much idea to this concept but it's really hard to believe that what a TechNet is ready to do in 4 cores it's possible to do in 2 cores.

    1. Hi,
      What TechNet fails to address is the use of SSD drives. Hosting a dev environment on an SSD disk hugely helps counter for less CPU cores and RAM. And for dev in a single user environment, cpu usage is not the killer for SharePoint. Of course, if you do search testing and indexing, CPU will have an impact. The question is always how much data are you dealing with in development.

      The better the hardware, the better the experience. But I'm saying my setup works to my satisfaction, meaning I don't have to sit around waiting most of the time.

  4. i think this is new framework of SharePoint so most of people don't know about SharePoint its great news and describes useful information for new users

  5. One of the few blogs which not talk about technical detail and every other part which is associated with coding standard of SharePoint but to the point talk about hardware requirement for the SharePoint development process.