1 / 67

Design, performance and capacity - Factors of successful intranet and internet SharePoint sites

Design, performance and capacity - Factors of successful intranet and internet SharePoint sites. Sanjay Narang, Anandan Kumaran , Singaram Murigappan. Agenda. Real Life Implementation – www. c ognizant.com Real Life Case Study – Capacity Planning Aspects Of Performance

jaeger
Télécharger la présentation

Design, performance and capacity - Factors of successful intranet and internet SharePoint sites

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. Design, performance and capacity - Factors of successful intranet and internet SharePoint sites Sanjay Narang, AnandanKumaran, SingaramMurigappan

  2. Agenda • Real Life Implementation – www.cognizant.com • Real Life Case Study – Capacity Planning • Aspects Of Performance • Capacity Management Model • Model • Design

  3. www.cognizant.com SharePoint 2010 Implementation

  4. Publish Content • Marketing team needs a robust mechanism to publish content effectively without needing specialized technical skill

  5. Content Deployment Authoring Pre-Production www.cognizant.com Content authored is saved in the authoring server database Content push by marketing admin Content authored is moved to the preproduction environment. It allows the user to verify the content before pushing live Content push by marketing admin Content is moved from preproduction environment to live environment after verification

  6. Intuitive User Interface

  7. Intuitive User Interface

  8. Content Authoring • nt Content Author needs a mechanism to add/edit content, upload documents without worrying about the layout or having pre-requisite design skills

  9. Author Content

  10. Edit Page

  11. Edit Page Contd.,

  12. Edit Page Contd.,

  13. Our Approach – Edit View

  14. Public View

  15. Friendly URLs Need for friendly URLs that are easier for users to remember and for search engines to find http://www.cognizant.com/banking-financial-services/Pages/landingPage.aspx

  16. URL Rewrite • Powerful rules to transform complex URLs into simple and consistent web addresses • Rule-based URL rewriting engine • Regular expression pattern matching • Downloadable • Download: • http://go.microsoft.com/?linkid=9722532

  17. Configuration - Inbound • Inbound rules convert the user friendly URLs provided by the users to actual URLs

  18. Configuration - Outbound • Outbound rules convert the actual URLs to the user friendly URLs

  19. Friendly URL - Output http://www.cognizant.com/banking-financial-services

  20. URL Rewrite Support Not officially supported by the Microsoft Product Team

  21. Faster Site Need for the site to equally responsive and quick to all users across the globe. The load of users on the application will vary especially during financial results but I need a cost effective solution

  22. SharePoint Out-Of-Box • Output Caching • Object Cache • This can load but not latency

  23. Content Delivery Network • Deliver content faster • Scalability • Across the globe users has similar experience on accessing the site

  24. Capacity Planning and Management

  25. Case Study – Contoso Intranet Portal • 150,000 users spread across globe • Existing site • The gateway to all other applications • primarily HTML/ASP/JavaScript • New site • Intranet Publishing on SharePoint Server 2010 • Widget based homepage, • Much more content on home page including Flash videos

  26. Capacity Management • Capacity Planning • One time sizing • Selection & Configuration • Data architecture • Topologies (physical and logical) • Hardware • Capacity Management • Extends Planning • Cyclic Process • Monitored & Optimized • Changing Conditions and Requirements

  27. Analogy

  28. Analogy

  29. Capacity Management Model

  30. Aspects of Performance • Latency • Throughput • Data Scale • Reliability

  31. capacity management Model

  32. Definitions and Conventions • Users • Concurrent Users • Active Users • RPS

  33. Definitions and Conventions • User Types

  34. Model • Determine Workload • Determine DataSet • Set Performance and Reliability Targets

  35. RPS Estimation (New Env) Number RPH/User RPH Total Users 150,000 Active Users 50,000 Light (10%) 5,000 20 100,000 Typical (70%) 35,00036 1260,000 Heavy (15%) 7,500 60 450,000 Extreme (5%) 2,500 120 300,000 Total RPH 2,111,000 RPS (RPH/3600) 586 Concurrency 50% Effective RPS 293

  36. RPS Calculations (Existing Env) • IIS Logs • Take from all servers into a central location • Take it for one of the peak day • User Tools • LogParser 2.2

  37. Get RPS per second logparser-i:IISW3C -o:CSV "SELECT QUANTIZE(TO_TIMESTAMP(date, time), 3600) AS Hour, QUANTIZE(TO_TIMESTAMP(date, time), 1) AS Second, COUNT(*) AS RPS INTORPS_No401s.csv FROM*.log WHEREsc-status <> 401 GROUP BY Hour, Second"

  38. RPS Every Second for 24 Hours

  39. Avg and Max RPS Every Hour for 24 Hours

  40. Avoid Image, CSS, JS • Get File Extension to_lowercase EXTRACT_EXTENSION(cs-uri-stem)) • exclude Where clause fext <> ‘jpg’ AND fext <> ‘jpeg’ AND fext <> ‘gif’ AND fext <> ‘png’ AND fext <> ‘js’ AND fext <> ‘css’

  41. Decision Point – Peak or Average • Average RPS on a day • Average RPS in a peak hour • Maximum RPS in a peak hour 220 700 1500

  42. Dataset - Content DB

  43. Content DB Calculations

  44. All Databases Calculations

  45. Overall SQL Server Storage

  46. Performance and Reliability Targets • Availability • Numbers of Nines (99%, 99.9%, 99.99%) • Consider • Patch Management • Code Releases • Server Responsiveness • E.g. < 1 sec • System Resource Utilization • E.g. Avg CPU < 50% , Available Memory

  47. Model - Summary • Total Number of Users – 150,000 • Total Request in a day – 18,000,000 • Throughput (RPS) – 1500, 700, 220 • Storage - 5 TB • Server Response Time < 1 sec

  48. capacity management Design

  49. Design • Identify case study • Choose an Architecture • Determine Hardware

  50. Know SharePoint 2010 • Vs SharePoint 2007 • Service Applications & Cross Farm Publishing • Oversizing vs. Undersizing • Reference Architectures • Single server, small, medium and large farms

More Related