1 / 16

Sydney SharePoint User Group

Sydney SharePoint User Group. Capacity Planning and stress testing SharePoint using the Visual Studio Team Suite. Steve Smith – MVP SharePoint Server Owner Combined Knowledge. Who am I . Co Owner of Combined Knowledge Ltd and Combined Knowledge Asia Pacific MVP for SharePoint Server

Audrey
Download Presentation

Sydney SharePoint User Group

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Sydney SharePoint User Group Capacity Planning and stress testing SharePoint using the Visual Studio Team Suite Steve Smith – MVP SharePoint Server Owner Combined Knowledge

  2. Who am I • Co Owner of Combined Knowledge Ltd and Combined Knowledge Asia Pacific • MVP for SharePoint Server • ISPA Lead for the EMEA • Co organiser UK SharePoint User Group • Nearly 4000 members  • Co Author of the SharePoint Administrators Companion

  3. Agenda • Understand why to use Visual Studio Team Suite 2008 • Demonstrate how to build a ‘test rig’ • Demonstrate how to baseline a SharePoint Server 2007 server farm • Understand how to test for the performance impact of adding Web parts • Demonstrate real-time monitoring • Demonstrate archival of results for later review

  4. Why Stress Test? • Visual Studio 2008 isn’t just for developers  • Ensure adequate resources • Servers, Network, WAN • Test performance impact of Web parts • Native, Custom, 3rd party • Test any major configuration change • Adding/Removing WFE Server to farm • Scaling Search and Indexing • Use SharePoint Planning and Capacity guides for design and architecture guidance.

  5. My Farm Setup • SharePoint Server 2007 64 bit • SQL Server 2005 • Visual Studio Team Suite 2008 • Windows Server 2008 64 bit WFE1 (web & query) WFE2 (web & query) MossApp Central Admin Index SQL Server

  6. Prepare VSTS 2008 • Setup Results Database on SQL Server 2005 • Remove default tests if desired • Setup the test controller and agents

  7. Build a Testing 'Rig’ • Requires VSTS 2008 • Must have one controller • Use multiple agents for better real-world load • Create new Project using the ‘Test Project’ template • Create Load test results store (DB) • Use loadtestresultsrepository.sql in ‘C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE’ to create database • Set loadtest database as the repository

  8. Create a VSTS 2008 Test Project & creating the SQL repository demo

  9. Record Web Tests • Choose Real world examples • Create many small tests, not one large one • Home page ‘read’ • Search query • List management • Upload Document • 404 • Test each one individually • Use Individual tests for Web parts, etc.

  10. Test Web Part Impact • Record Web test for the hosting page • Baseline load time • Change run settings to test browser version and WAN clients • Load Web part • Test response time • Should not be used for production testing, but will give you a good idea of Web part impact

  11. Record Web Tests and view the impact of adding a Web part to the home page demo

  12. Create Load Test • Create load test using one or more Web tests • Choose % mix for your environment • For new implementations or complete unknowns, use the posted mix on TechNet • Document Load Test Settings • Be sure to use the same settings when comparing baselines and changes • Create Peak and off-peak baselines • Use Systems Center Operations Manager 2007 to monitor actual usage for baselines

  13. Load Test Settings • Use intelligent names • Create a load pattern • Step load or constant load • Add previously recorded Web tests • That’s why we did those in small samples! • Choose Browser mix • Always use LAN for comparing to baseline • Add counter sets to monitor • Create custom counter sets later, if needed

  14. Aggregate Web tests for a single Load test and view results demo

  15. Reading the Results • Processor time and Disk I/O are critical • Use Systems Center Operations Manager 2007 management pack documents for performance counters to monitor during tests • Load Test Summary is useful • Add custom counters for Search, etc.

  16. Thanks for attendingQuestions?Contact details –steve@combined-knowledge.comwhitepaper –http://www.combined-knowledge.com.au/Downloads%202007.htm

More Related