SharePoint Global Deployment with Joel Oleson


Published on

SharePoint Global Deployments can be daunting. When you have all the information it doesn't need to be difficult to decide between the three most common deployments, centralized, regional, and distributed. With WAN data and application scenarios with performance requirements you can solve this often difficult decision.

Published in: Technology
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • 06/06/09 16:32 © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
  • SharePoint Global Deployment with Joel Oleson

    1. 1. SharePoint Global Deployment Joel Oleson Sr. Technical Product Manager Session Code:
    2. 2. <ul><li>7+ Year SharePoint Veteran </li></ul><ul><li>5 Years in MS IT </li></ul><ul><li>2 Years in Product Team </li></ul><ul><li>SharePoint Consultant and Trainer </li></ul><ul><li>5 yrs TechEd US & Europe </li></ul><ul><li>Globe Trotter </li></ul><ul><li>Ate crickets last week </li></ul>Who is SharePoint Joel?
    3. 4. Objectives And Takeaways <ul><li>Design Geo-distributed SharePoint Deployments </li></ul><ul><li>O ptimize the user experience </li></ul><ul><li>Deal with network latency and improve the general performance of the solution. </li></ul>
    4. 5. Agenda <ul><li>Geo Dilemma </li></ul><ul><li>Deployment Options </li></ul><ul><li>Information Architecture </li></ul><ul><li>Search Architecture for the WAN </li></ul><ul><li>Optimizing for the WAN </li></ul><ul><li>WAN Performance testing </li></ul>
    5. 6. Geo Dilemma To distribute or not distribute is the question <ul><li>Cost vs. Usability </li></ul><ul><li>Bandwidth can be bought but latency is bound to laws of physics </li></ul><ul><li>Different stakeholders -> different priorities/preferences </li></ul><ul><ul><li>IT tends to favor Centralized (low cost) </li></ul></ul><ul><ul><li>Business just wants it to work (faster the better) </li></ul></ul>
    6. 7. Agenda <ul><li>Geo Dilemma </li></ul><ul><li>Deployment Options </li></ul><ul><li>Information Architecture </li></ul><ul><li>Search/Indexing Architecture for the WAN </li></ul><ul><li>Optimization Techniques </li></ul><ul><li>WAN Performance Testing </li></ul>
    7. 8. Deployment Options <ul><li>Central solution </li></ul><ul><li>Regional solution </li></ul><ul><li>Distributed solution </li></ul>
    8. 9. Central Solution
    9. 10. Central Deployment with a twist Partner Solution: WAN Acceleration REDMOND WAN Accelerator Datacenter All Services in one Central Farm Central Search Central Directory WAN Accelerator remote office BEIJING 10s-100s of Local WAN Accelerators ~5x - 1 st Request ~43x - 2 nd Request
    10. 11. Sampling of WAN Optimization Partners <ul><li>WAN Accelerators </li></ul><ul><ul><li>Cisco </li></ul></ul><ul><ul><li>Citrix </li></ul></ul><ul><ul><li>Certeon </li></ul></ul><ul><ul><li>Packeteer </li></ul></ul><ul><ul><li>Riverbed </li></ul></ul><ul><ul><li>F5 </li></ul></ul><ul><li>Cache Devices </li></ul><ul><ul><li>Cisco </li></ul></ul><ul><ul><li>F5 </li></ul></ul><ul><ul><li>Inktomi </li></ul></ul><ul><ul><li>ISA and IAG Server </li></ul></ul><ul><li>Offline Client Solutions </li></ul><ul><ul><li>Groove </li></ul></ul><ul><ul><li>Colligo </li></ul></ul><ul><li>Data Replication </li></ul><ul><ul><li>Syntergy </li></ul></ul><ul><ul><li>WinApp Technologies </li></ul></ul><ul><ul><li>Casahl </li></ul></ul><ul><ul><li>Infonic </li></ul></ul><ul><li>Multi-farm management </li></ul><ul><ul><li>Quest Software </li></ul></ul><ul><ul><li>EchoTechnologies </li></ul></ul><ul><ul><li>IDevFactory </li></ul></ul><ul><ul><li>AvePoint </li></ul></ul><ul><ul><li>CorasWorks </li></ul></ul><ul><ul><li>Barracuda Tools </li></ul></ul><ul><ul><li>CommVault </li></ul></ul><ul><ul><li>Symantec </li></ul></ul><ul><li>Byte Level Replica </li></ul><ul><ul><li>Neverfail </li></ul></ul><ul><ul><li>Double-take </li></ul></ul><ul><li>SAN Replication </li></ul><ul><ul><li>HP </li></ul></ul><ul><ul><li>EMC Centera </li></ul></ul><ul><ul><li>Hitachi Data Systems </li></ul></ul>
    11. 12. Central Solution <ul><li>Easiest to maintain and operate. </li></ul><ul><li>Cheapest Solution </li></ul><ul><li>Easiest to support </li></ul><ul><li>Is it the Utopia? - Don’t forget D/R!!! </li></ul>
    12. 13. Key Network Considerations <ul><li>Latency #1 </li></ul><ul><li>Bandwidth #2 </li></ul><ul><li>Utilization (is it already high % consumed?) </li></ul><ul><li>Expected use of MOSS (page sizes, file sizes, and usage patterns) </li></ul>
    13. 14. Other Network Considerations <ul><li>Politics (AD trusts/Affiliates) Deloitte </li></ul><ul><li>Business Requirements (Speed comfort) Energizer </li></ul><ul><li>Network Map (Microsoft) </li></ul><ul><li>Network Roadmap & Datacenter Consolidation Goals (HP) </li></ul>
    14. 15. Regional Deployment Optimized Network Bandwidth/Latency REDMOND DUBLIN SINGAPORE <ul><li>Regional Scope Services </li></ul><ul><li>Local Office Server Farms (Intranet only) </li></ul><ul><li>Local SSP Farm </li></ul><ul><li>Centrally Managed from Redmond </li></ul><ul><li>Enterprise Scope Services </li></ul><ul><li>Local Office Server Farms (Intranet and Extranet) </li></ul><ul><li>Local SSP Farm </li></ul><ul><li>Centrally Managed from Redmond </li></ul><ul><li>Regional Scope Services </li></ul><ul><li>Local Office Server Farms (Intranet and Extranet) </li></ul><ul><li>Local SSP Farm </li></ul><ul><li>Centrally Managed from Redmond </li></ul>
    15. 16. Regional Deployments Central site hosts for regional sites Regional sites host <ul><li>Server farm running MOSS including: </li></ul><ul><li>Published intranet content. </li></ul><ul><li>Enterprise-wide search (optional). </li></ul><ul><li>My Site redirection (Trusted My Site Host Location). This ensures that a user coming from a regional farm is redirected to the My Site on the farm where their profile resides. </li></ul><ul><li>Profile synchronization. </li></ul><ul><li>Aggregation of content developed at regional sites based on workflow and policies. </li></ul><ul><li>Server farm running MOSS, including: </li></ul><ul><li>Team or division collaboration sites. </li></ul><ul><li>My Sites with My Site redirection. This ensures that a user coming from the central farm or another regional farm is redirected to the My Site where their profile resides. </li></ul><ul><li>Search for local content. </li></ul>
    16. 17. Why Go Regional? <ul><li>If you are unable to optimize the central solution to improve WAN performance to acceptable levels. </li></ul><ul><li>Provides fast access to services that regional users are likely to use most —collaboration sites and My Sites. </li></ul><ul><li>Provides separate deployments for geo-political or compliance related </li></ul>
    17. 18. Why Not Go Regional? <ul><li>Regional provides more overhead and backup complexity – more environments to support </li></ul><ul><li>Difficult to get Indexing to work as you’d want it to over the WAN (consumes Bandwidth) </li></ul><ul><li>Shared Services such as BDC and Profiles can’t be shared </li></ul>
    18. 19. Distributed- Multiple Deployments with Consolidation Search where possible Denver HQ Central Portal MOSS farm for Enterprise Search Branch Office MOSS or WSS Deployments BANGALORE Disconnected or Bandwidth Constrained or Autonomy
    19. 20. Distributed Central site hosts for regional sites Local/Distributed sites host <ul><li>Server farm running MOSS, including: </li></ul><ul><li>Published intranet content </li></ul><ul><li>Aggregation of some local content </li></ul><ul><li>My Site redirection and profile synchronization if MOSS is used at the regional sites. </li></ul><ul><li>Either: </li></ul><ul><li>Server farm running MOSS, including: </li></ul><ul><ul><li>Team collaboration </li></ul></ul><ul><ul><li>Regional or Aggregated My Sites </li></ul></ul><ul><ul><li>Search for local content </li></ul></ul><ul><ul><li>Read-only copy of published intranet content (optional) </li></ul></ul><ul><li>Server farm running WSS including: </li></ul><ul><ul><li>Team or division collaboration sites. </li></ul></ul><ul><ul><li>WSS Search </li></ul></ul>
    20. 21. Why go Distributed? <ul><li>Recommended for organizations that have many offices distributed geographically, such as branch offices. </li></ul><ul><li>Fastest possible access to most remote users </li></ul><ul><li>Bandwidth challenged </li></ul><ul><li>Autonomous organizations can find MOSS Central brings distributed deployments together </li></ul>
    21. 22. Why Not? <ul><li>It’s the easiest to decide (because the business wants fast), but hardest to get working right </li></ul><ul><li>Most amount of support </li></ul><ul><li>Most complex for operations </li></ul><ul><li>Can be confusing for users with cross group/cross location collaboration </li></ul>
    22. 23. Determining Latency and Page and File Elements Simple network tools… Using the power of Ping Wfetch and Fiddler
    23. 24. Key Considerations… Reinforced. <ul><li>Know your usage </li></ul><ul><ul><li>Intranet publishing portal </li></ul></ul><ul><ul><li>Collaboration </li></ul></ul><ul><ul><li>BI, reporting </li></ul></ul><ul><li>Know your network </li></ul><ul><ul><li>Bandwidth </li></ul></ul><ul><ul><li>Latency </li></ul></ul><ul><ul><li>Utilization </li></ul></ul><ul><li>Include tests and Surveys* from remote offices </li></ul>
    24. 25. Agenda <ul><li>Geo Dilemma </li></ul><ul><li>Deployment Options </li></ul><ul><li>Information Architecture </li></ul><ul><li>Search Architecture for the WAN </li></ul><ul><li>Optimizing for the WAN </li></ul><ul><li>WAN Performance Testing </li></ul>
    25. 26. Plan for Information Management <ul><li>Usage profiles </li></ul><ul><ul><li>Company/enterprise wide use </li></ul></ul><ul><ul><li>Team use </li></ul></ul><ul><ul><li>Personal use </li></ul></ul><ul><li>Life Cycle </li></ul><ul><ul><li>Cross X Collaboration </li></ul></ul><ul><ul><li>Publishing-Content is authored by few and shared broadly. </li></ul></ul><ul><ul><li>Archive – infrequent to no access </li></ul></ul>
    26. 27. Plan for Global Collaboration <ul><li>Centralized vs. Distributed </li></ul><ul><li>Global or local teams </li></ul><ul><ul><li>Where to put the sites </li></ul></ul><ul><li>End user experience </li></ul><ul><ul><li>Bandwidth/Latency </li></ul></ul><ul><li>Operational costs </li></ul><ul><li>Search </li></ul><ul><li>Offline </li></ul><ul><ul><li>Groove, Outlook, etc. </li></ul></ul><ul><li>Network accelerators </li></ul><ul><ul><li>Security, ACLs </li></ul></ul>
    27. 28. Agenda <ul><li>Geo Dilemma </li></ul><ul><li>Deployment Options </li></ul><ul><li>Information Architecture </li></ul><ul><li>Search Architecture for the WAN </li></ul><ul><li>Optimizing for the WAN </li></ul><ul><li>WAN Performance Testing </li></ul>
    28. 29. Global Scale Search <ul><li>Centralized vs. Distributed farms </li></ul><ul><ul><li>Crawling across the wire </li></ul></ul><ul><ul><ul><li>vs. </li></ul></ul></ul><ul><ul><ul><li>Querying across the wire </li></ul></ul></ul><ul><ul><li>Crawling external content </li></ul></ul><ul><ul><ul><li>Protocol handlers </li></ul></ul></ul><ul><ul><ul><li>iFilters </li></ul></ul></ul><ul><ul><li>Partitioning data </li></ul></ul><ul><ul><ul><li>Based on Geography vs. Content </li></ul></ul></ul><ul><ul><li>Federating results </li></ul></ul><ul><ul><ul><li>Merging results from different indexes loses relevancy </li></ul></ul></ul>
    29. 30. Search architectures for WAN environments <ul><li>Centralized Search </li></ul><ul><li>Regionalized Search </li></ul><ul><li>Distributed Search </li></ul><ul><li>Federated Search </li></ul>
    30. 31. Search architectures for WAN environments Centralized search <ul><li>The central SSP crawls all the content in the local farm </li></ul><ul><li>Regional queries are sent to the central farm </li></ul><ul><li>Pros: </li></ul><ul><ul><li>Centralized management </li></ul></ul><ul><ul><li>World-wide relevancy </li></ul></ul><ul><li>Cons: </li></ul><ul><ul><li>Crawling/Querying across the wire </li></ul></ul><ul><ul><li>Index freshness if regional content changes frequently </li></ul></ul><ul><ul><li>Need manual redirection </li></ul></ul>
    31. 32. Regionalized Search <ul><li>Each region hosts its own SSP </li></ul><ul><li>Each SSP only crawls local content </li></ul><ul><li>Search URLs for each Region </li></ul><ul><li>Pros: </li></ul><ul><ul><li>No crawling across the wire </li></ul></ul><ul><li>Cons: </li></ul><ul><ul><li>Search is regionalized </li></ul></ul><ul><ul><li>Users must know which farm to search </li></ul></ul>
    32. 33. Distributed Search <ul><li>Localized </li></ul><ul><li>Central Site crawls Local Farms (where possible) </li></ul><ul><li>Pros: </li></ul><ul><ul><li>Central has global relevancy </li></ul></ul><ul><ul><li>Regional users can view regional results </li></ul></ul><ul><li>Cons: </li></ul><ul><ul><li>local users must use Central Search for global search </li></ul></ul><ul><ul><li>Dual crawling or more… </li></ul></ul>
    33. 34. Federated Search <ul><li>Each region hosts its own SSP </li></ul><ul><li>Each region configured to crawl itself and Federated Search Queries to other regions </li></ul><ul><ul><li>SSP is configured to crawl other farms based on the business needs </li></ul></ul><ul><li>MOSS2007 SP1 + Infra Update </li></ul><ul><li>Pros: </li></ul><ul><ul><li>Query performance optimized locally </li></ul></ul><ul><ul><li>Content is crawled once </li></ul></ul><ul><ul><li>Asynchronous queries over WAN </li></ul></ul><ul><li>Cons: </li></ul><ul><ul><li>Relevancy is weighted </li></ul></ul><ul><ul><li>Multiple SSPs to manage </li></ul></ul>
    34. 35. Agenda <ul><li>Geo Dilemma </li></ul><ul><li>Deployment Options </li></ul><ul><li>Information Architecture </li></ul><ul><li>Search Architecture for the WAN </li></ul><ul><li>Optimizing for the WAN </li></ul><ul><li>WAN Performance Testing </li></ul>
    35. 36. End-to-End Perceived Network Performance <ul><li>Client Performance: </li></ul><ul><li>CPU/Processor Delay </li></ul><ul><li>Virtual/Physical Memory Limits </li></ul><ul><li>NIC Config, Network Drivers and TCP/IP Config </li></ul><ul><li>Client Application Versions </li></ul><ul><li>Proxy Config </li></ul><ul><li>Client-side LAN Performance: </li></ul><ul><li>Switch Config </li></ul><ul><li>Contention for Uplink </li></ul><ul><li>WAN: </li></ul><ul><li>Link Speed(Bandwidth) </li></ul><ul><li>Delay (Latency) </li></ul><ul><li>Packet Loss, Retransmissions, Timeouts </li></ul><ul><li>Network Throughput </li></ul><ul><li>Round Trips </li></ul><ul><li>Concurrency </li></ul>Server-Side LAN Performance: Switch Config Contention for Uplink Server Performance: CPU/Processor Delay Virtual and Physical Memory Limits NIC/Network Drivers and TCP/IP config Network Speed (10/100/1000MB) Server Software Layer
    36. 37. End to End Examples
    37. 38. Crawling has IMPACT <ul><li>Commonly 50% of Traffic </li></ul><ul><li>Use Dedicated WFE for crawling; remove from NLB rotation </li></ul><ul><li>Combine Index Server with Web server role (hosts) </li></ul>
    38. 39. SharePoint to SharePoint Crawl
    39. 40. File Server Crawl Rates
    40. 41. HTTP Crawl Rates
    41. 42. Intranet Recommended Bandwidth Centralize Regional Deployments Distributed Bandwidth ranges of 3Mbps (Dual T1) and above with latencies no greater than ~150 milliseconds with large offices (well connected) Bandwidth ranges of 1.5Mbps (T1) and above with latencies no greater than 100 msecs (*Well connected with hubs) Disconnected and/or limited bandwidth with large groups of users or no AD trust organizations (*non trusting disconnected, autonomous or high speed requirements)
    42. 43. What Do SharePoint Server and Donald Trump Have in Common? Courtesy
    43. 44. Cache! TechNet: (Cache Settings) Additional performance and capacity factors
    44. 45. Cache
    45. 46. Cache Config Levels <ul><li>Web App – Disk based caching in web.config </li></ul><ul><li>Site collection – configure output cache and object cache settings </li></ul><ul><li>Site – output cache settings </li></ul><ul><li>Page layout – output cache </li></ul><ul><li>Web Part – settings in dwp code </li></ul><ul><li>Query – i.e. RSS Feed cache is 5 min by default, cross list query </li></ul>
    46. 47. Cache Recommendations <ul><li>Cache is but…. </li></ul><ul><ul><li>Setting memory based caching can waste valuable memory (ASP.NET may flush cache to make room!) </li></ul></ul><ul><ul><li>Never cache search results – disable search results layout page cache </li></ul></ul><ul><ul><li>Never cache personalized web parts </li></ul></ul>
    47. 48. Optimizing for the WAN <ul><li>Page optimization techniques </li></ul><ul><ul><li>Use BLOB cache </li></ul></ul><ul><ul><li>Use IIS Compression for dynamic pages </li></ul></ul><ul><ul><li>Minimize images sizes and count </li></ul></ul><ul><ul><li>Delay downloading of core.js </li></ul></ul><ul><ul><li>Optimize list view pages (allitems.aspx) </li></ul></ul><ul><ul><li>Use Fiddler ( ) </li></ul></ul><ul><li>Index Optimization </li></ul><ul><ul><li>Specialize crawl time schedules for WAN links </li></ul></ul><ul><ul><ul><li>Increase time-out settings for search </li></ul></ul></ul><ul><ul><ul><li>Crawler impact rules/ # crawl threads </li></ul></ul></ul>
    48. 49. Dev Techniques for the WAN <ul><li>Optimizing Web Parts for the WAN </li></ul><ul><ul><li>Re-use built-in Styles vs. Creating Custom Styles </li></ul></ul><ul><ul><li>Storing State </li></ul></ul><ul><ul><ul><li>Use Server Cache class </li></ul></ul></ul><ul><ul><ul><li>Web.config: enableViewState=true </li></ul></ul></ul><ul><ul><ul><li>Use Control State </li></ul></ul></ul><ul><ul><ul><ul><li>Page.RegisterRequiresControlState() </li></ul></ul></ul></ul><ul><ul><ul><ul><li>LoadControlState(), SaveControlState() </li></ul></ul></ul></ul><ul><ul><li>Maximize perf on Webparts displaying data </li></ul></ul><ul><ul><ul><li>Use inline XML data islands </li></ul></ul></ul><ul><ul><ul><li>Use Client-Side scripts to connect to Webservices </li></ul></ul></ul><ul><ul><ul><li>AJAX and JSON is lightweight </li></ul></ul></ul>
    49. 50. LAN Farms not WAN <ul><li>Conditions for supported configuration: </li></ul><ul><ul><li>WFE  1 millisecond(ms) latency  DB </li></ul></ul><ul><ul><li>All servers on the same network segment </li></ul></ul><ul><ul><ul><li>Same VLAN </li></ul></ul></ul><ul><ul><ul><li>No router switching </li></ul></ul></ul><ul><ul><li>SSPs in the same datacenter </li></ul></ul><ul><ul><li>Servers cannot cross time zones </li></ul></ul>
    50. 51. Agenda <ul><li>Geo Dilemma </li></ul><ul><li>Deployment Options </li></ul><ul><li>Information Architecture </li></ul><ul><li>Search Architecture for the WAN </li></ul><ul><li>Optimizing for the WAN </li></ul><ul><li>WAN Performance Testing </li></ul>
    51. 52. WAN Test Hardware – MTC Austin <ul><li>SAN </li></ul><ul><ul><li>EMC CLARiiON CX700 </li></ul></ul><ul><ul><ul><li>30 x 73GBytes spindles @10,000RPM FC </li></ul></ul></ul><ul><ul><ul><li>10 spindles/LUN </li></ul></ul></ul><ul><ul><ul><li>3 LUNs, RAID 10 </li></ul></ul></ul><ul><li>SQLServer </li></ul><ul><ul><li>Dell PowerEdge 6950 </li></ul></ul><ul><ul><ul><li>4 x Dual-Core AMD Opterons 2.60GHz </li></ul></ul></ul><ul><ul><ul><li>32 GB RAM </li></ul></ul></ul><ul><ul><ul><li>SQL Server 2005 64-bit w/ SP2 </li></ul></ul></ul><ul><li>WFE </li></ul><ul><ul><li>Dell PowerEdge 2950 </li></ul></ul><ul><ul><ul><li>2 x 3.0 GHz Dual-core Intel Xeon Processors </li></ul></ul></ul><ul><ul><ul><li>16 GB RAM </li></ul></ul></ul><ul><ul><ul><li>MOSS 32-bit </li></ul></ul></ul><ul><li>WAN Accelerator </li></ul><ul><ul><li>Shunra VE STN </li></ul></ul>
    52. 53. Test Topology
    53. 54. User Operations Test Mix Common User Operation Mix Description Percentage WSSHomePage Browse to the site’s homepage 25% WSSSmallDocLibAllItems Browse to all items view of a Document Library 14% WSSDocHTTPFetch Download a document via the browser 12% WSSGetListPageHtml View all items in a list 12% WSSSearch Search of pre-define search terms 11% WSSRSSList Read from an RSS list feed 10% WSSDispForm List Item view 9% WSSOutlookSync Perform a SOAP call to WSS to update a SharePoint List update in Outlook 7%
    54. 55. Page Load Times – Common User Operation Concurrency: Bandwidth (Mbps) 50 100 500 1000 10,000 Utilization (%) Throughput (Kbps) 45 (T3), Latency = 50ms 1.17 1.17 1.18 1.20 1.23 12 – 15 225 – 281 45 (T3), Latency = 100ms 1.87 1.90 1.90 1.90 1.90 7 – 9 134 – 174 45 (T3), Latency = 250ms 4.00 4.07 4.14 4.16 4.16 4 - 8 79 – 90 45 (T3), Latency = 500ms 7.50 7.50 7.70 7.90 7.90 2 – 4 35 - 48 12 (8 T1s), Latency = 50ms 1.31 1.34 1.35 1.36 1.37 43 – 48 231 - 260 12 (8 T1s), Latency = 100ms 2.03 2.03 2.04 2.07 2.08 30 – 32 156 - 180 12 (8 T1s), Latency = 250ms 4.14 4.20 4.25 4.26 4.35 13 – 15 75 – 86 12 (8 T1s), Latency = 500ms 7.60 7.70 7.80 7.80 7.90 6 – 9 40 - 50 6 (Quad T1), Latency = 50ms 1.93 1.94 1.94 1.97 1.88 69 - 72 184 - 203 6 (Quad T1), Latency = 100ms 2.27 2.34 2.37 2.38 2.40 53 - 60 144 - 162 6 (Quad T1), Latency = 250ms 4.20 4.21 4.28 4.35 4.46 22 – 32 62 - 90 6 (Quad T1) Latency = 500ms 7.70 7.90 7.90 8.10 8.10 15 – 18 43 - 50 3 (Dual T1), Latency = 50ms 3.40 3.43 3.55 3.61 3.65 65 - 90 90 - 124 3 (Dual T1), Latency = 100ms 3.57 3.59 3.68 3.69 3.72 64 – 85 88 - 116 3 (Dual T1), Latency = 250ms 4.51 4.57 4.68 4.71 4.79 44 - 60 61 - 82 3 (Dual T1), Latency = 500ms 7.70 8.00 8.00 8.10 8.20 27 – 35 40 - 50 1.5 (T1), Latency = 50ms 6.40 7.20 7.40 7.50 7.50 85 - 95 62 - 66 1.5 (T1), Latency = 100ms 6.50 7.10 7.20 7.20 7.60 72 - 86 52 - 60 1.5 (T1), Latency = 250ms 7.00 7.10 7.20 7.30 7.40 75 – 84 52 - 60 1.5 (T1), Latency = 500ms 8.40 8.50 8.70 8.80 8.90 60 – 65 42 - 47 0.5 (512K), Latency = 50ms 18.20 18.90 20.40 20.40 22.00 80 – 98 19 - 24 0.5 (512K), Latency = 100ms 18.30 18.90 20.40 20.40 22.00 80 – 96 18 - 24 0.5 (512K), Latency = 250ms 18.50 18.80 19.60 20.80 21.10 78 - 90 21 - 24 0.5 (512K), Latency = 500ms 18.80 19.00 20.00 21.90 22.70 73 - 92 17 - 22
    55. 56. Page Load Time: Common User Operation
    56. 57. Thank You!