Custom Solutions and Capacity Management Part 1

This is a live blogging post from the International SharePoint Conference London 2012. So don’t expect well-written proza here.

Session by Steve Smith, Ben Curry

Demo-heavy session


  • recap & overview of the SharePoint architecture and the conference hardware setup
  • web applications & site collections are naturally the first things to test
  • finding a balance between software boundaries is key, don’t go about with 300 content databases of 4 TB each
  • consider adding extra (dedicated) SQL server instances to scale your environment

Load Test Demo

  • loadtestresultrepository.sql on the visual studio to create a database for tests & results
  • you can use Fiddler to construct your tests and export them for use in visual studio (export sessions to VS WebTest)
  • create the database and create the test project in VS Ultimate afterwards
  • you could also add client machines to use as test agents to help in your testing
  • there is a feature pack on your MSDN subscription to be able to have 250 concurrent test connections
  • create a web performance test to capture website interactions
  • you can use external data sources (e.g. csv) as input variables to create more realistic tests (e.g. different users)
  • don’t forget to test edge cases or stuff that is expected not to work
  • next create a load test to run your web tests
  • use a small & simple load test in the beginning to get a basic understanding of the farm quality
  • after implementing social features & office workspace concurrency rates of 30% are not rare anymore!
  • don’t underestimate the amount of search queries being fired by webparts on your homepage, not all searching is done interactively by users in the search box
  • make sure you have admin access from your test box to the servers in the farm in order to capture perfmon counters