Presentation on theme: "Architecting the Network for SharePoint"— Presentation transcript:
1Architecting the Network for SharePoint 20102007 Presented byMichael KoyfmanSolution Architect
2Q110 Gartner ADC Market Share F5 Continues to be #1 in the WW Application Delivery Controller Market for Q110Q110 Gartner ADC Market ShareQ110 ADC* Market Share LeadersF5 : 44.2%Cisco: 22.4%Citrix: 10.6%Q110 ADC Market Share Revenue LeadersF5: $126.4 MillionCisco: $64 MillionCitrix: $30.4 MillionQ110 ADC Q/Q Revenue GrowthF5: 12.5%Cisco: -8.6%Citrix: -15%Q110 ADC Total Market NumbersRevenue: $285.7 MillionQ/Q Revenue Growth: 1%*Application Delivery Controller (ADC) Segment Includes: Server Load Balancing/Layers 4-7 Switching and Advanced (Integrated) PlatformsCitrix10.6%Radware8.8%Cisco22.4%Others13.9%F5 NETWORKS44.2%SOURCE: Gartner
3F5 Dominates in Advanced Platform ADC Segment for Q110 Q110 Gartner Advanced Platform ADC Market ShareQ110 Advanced Platform ADC* Market Share LeadersF5: 61%Citrix: %Radware: 10.5%Q110 Advanced Platform ADC Market Share Revenue LeadersF5: $126.4 MillionCitrix: $30.4 MillionRadware: $21.7 MillionQ110 Advanced Platform ADC Q/Q Revenue GrowthF5: %Citrix: -15%Radware: 2.4%Q110 Advanced Platform ADC Total Market NumbersRevenue: $207.1 MillionQ/Q Revenue Growth: 4.3%*Advanced Platform Segment Includes: ADCs that integrate several functions (typically more than four) on a single platform (for example, load balancing, TCP, connection management, SSL offload, compression and caching)Radware10.5%Others13.8%Citrix15.7%F5 NETWORKS61%SOURCE: Gartner
4Leadership PositionMagic Quadrant for Application Delivery Controllers, 2009F5 Networks - StrengthsF5 Networks has a broad and comprehensive vision with industry-leading understanding of the needs of application development, deployment and management.The vendor has a comprehensive feature set with a full range of extensibility delivered through iRules and iControl, and integration with popular integrated development environments (IDEs), such as Eclipse and .NET/Visual Basic.F5 has developed a very large community of committed users (using F5's DevCentral portal) that helps fuel the use of iRules to solve unique data center application challenges, creating a loyal and engaged user base.F5 has a solid financial position and continued market-leading position.SOURCE Link
5The Leader in Application Delivery Networking UsersApplicationDeliveryNetworkDatacenterAt HomeIn the OfficeOn the RoadSAPMicrosoftOracle
6Purpose: How can the Network be Leveraged to achieve: ScalabilityBuilding the Right Infrastructure to Meet the Current User Load, and Also Allow for Future Growth.High AvailabilityArchitecting the “Bullet Proof” SharePoint DeploymentEradicating the Single Points of FailurePerformanceBuilding a SharePoint Deployment with the Best Possible End User Experience
7Load Balancing Concepts User RequestsThe Typical Single Server DeploymentUsers connect directly to the open IP:Port of the ServerNo redundancy, little scalabilitySingleServer
8Load Balancing Concepts Introduction of the Load BalancerHardware DeviceDifferent models for capacitySits in front of the server farm, accepting the user connections, and then dispatching the connection to a chosen server.Most modern LBs are multi-function(caching, compression, rate shaping, firewalling, etc…)Most LBs can load balance multiple types of trafficUser RequestsFarm ofServersInstead of a single server, a Load Balancer allows you to scale the number of available servers
9Load Balancing Concepts How it works:A properly configured Load Balancer is constantly monitoring the health and availability of the servers in the farm. It will use this information to help it make a load balancing decision.Instead of the User making the connection directly to the server, the User makes a connection to the Virtual Server, which resides on the external facing side of the Load BalancerThe Load Balancer will send the connection to a specific server based uponThe LB algorithm selectedHealth & Availability of the serversUser RequestsFarm ofServers
10Load Balancing Concepts Load Balancing Methods:Some are staticRound RobinRatioSome are dynamic, and try to take certain network and server characteristics into accountLeast ConnectionsFastest ServerTrendingUser RequestsFarm ofServersHistorically, static methods were preferred, as they tended to have the lightest impact on the Load Balancer, however today’s Load Balancers are capable of handling even complex LB algorithms without any performance degradation. F5 recommends using a dynamic LB method with SharePoint.
11Load Balancing Concepts Persistence:Once a user is sent to a specific server, do follow on connections/requests need to be sent to the same server?Common Persistence Methods:Source IP BasedCookie BasedSSL IDCustom MethodsUser RequestsFarm ofServersMost SharePoint deployments do not require persistence, however since a SharePoint front end can build an object cache, there is benefit to enabling it. It’s recommended to use a combination of Cookie & Source IP based persistence.
12Load Balancing Concepts Leveraging a Load Balancer to Eliminate the Single Points of FailureRedundant Load BalancersInstant failoverShare stateRedundant & Meshed Switch ArchitectureNo single path out to the next hopSpanning Tree supportMultihomed NetworksMultiple ISP links into the Data CenterMultiple Data Centers“Global” load balancingUser RequestsFarm ofServersIs it possible to eliminate all the Single Points of Failure?Is ‘5 9s of uptime’ achievable? Realistic?
13What Else Can My Load Balancer Do? *Differs by vendor, but most include technologies to alleviate server load, accelerate traffic, and minimize bandwidth utilization.User RequestsSSL terminationCompressionContent SpoolingTCP multiplexingTCP optimizationsBrowser optimizationsRate shapingIntelligent Browser Referencing (caching at the browser)Results from using these features with SharePoint 2007 can be found hereFarm ofServers
14Real-World Performance 350 Million Page Hits in 1 Week1/3 Reduction in Servers1/3 Reduction in Licenses1/3 Reduction in Management Time114.8Million595% Fewer Connections1.87Terabyte621Gigabytes66%Reduction inBandwidth3Seconds1200% FasterEnd-to-EndPage LoadTime14
16The Single SharePoint Server Deployment User RequestsNo RedundancyComplete failure with any pieceNo ScalabilityMeasurable maximum capacity50 to 75 Requests per second maxPerformance ConcernsEarly performance degradationSingle Server:Web ServerApplication ServerDatabaseNo Direct Upgrade from a stand alone to a farmMSFT – SSD is good for evaluation, deployments with minimal number of sites and you want to minimize overheadMicrosoft on the Single Server DeploymentGood for evaluationGood for very small deploymentsBenefit of minimal overhead
17Scaling Out The Deployment “The Small Server Farm”Common initial deploymentDatabase split from Front End ServersMeets requirements for HAAllows for future scalability175 to 250 RPS MaximumFront End Servers are responsible forServicing web requestsApplication Services, such asSearchingIndexingUser RequestsEach Server RunningWeb ServerApplication RolesClustered or MirroredSQL DatabaseSource :
18Scaling Out The Deployment “The Medium Server Farm”Same as the Small Server Farm, however the Application Server has been split from the Web Servers175 to 250 RPS MaximumAllows the Application Server’s CPU intensive functionality (search, excel services, etc) to have dedicated CPU cyclesUser RequestsWeb ServersApplication ServerClustered or MirroredSQL DatabaseSource:
19Scaling Out The Deployment “The Large Server Farm”All Servers, including Web, Application, and DB are scaled to meet demandCan scale to support “Hundreds of thousands of users”Availability Work Sheet from MicrosoftUser RequestsWeb ServersLoad Balancing of Application Servers is also possibleApplication ServersClustered or MirroredSQL DatabaseSource:
20Scalability – The Art of Sizing The Challenge is to size the deployment appropriatelyHow many servers are needed?How are the server roles split?What type of hardware should be used?The 2 Sided Sizing DilemmaMicrosoft can’t give precise sizing guidelinesCustomers can’t precisely profile their user baseFortunately, the amount of accurate and reliable sizing information is dramatically increasing
21Scaling the Network vs. Scaling the Servers What needs to be considered when sizing? Is scaling a server infrastructure linear with scaling the network?Considerations for server sizing includeHow many total users?How many concurrent users on average?Typical behavior of users? Posting, searching…. Etc.How many page views per person?How many users at peak times?How many sites are planned?What hardware architecture is being used?Considerations for network sizing includeWhat are the peak new connections per second?What is the peak number of users/connections?What is the peak bandwidth being consumed?How many servers is the Load Balancer responsible for monitoring?What else will the Load Balancer be doing? Caching, Compression……etc
22BIG-IP Hardware Line-up 2 x Hex core CPU16 10/100/ x 10 SFP+ 10Gbps2x 320 GB HD (S/W RAID) + 8GB CF32 GB memory100K TPS / 15Gb bulk12 Gbps max software compression40 Gbps TrafficBIG-IP 8950BIG-IP 89002 x Quad core CPU16 10/100/ x 1GB SFP + 2x 10Gb SFP+2x 320 GB HD (S/W RAID) + 8GB CF ?16 GB memory56K TPS / 9.6Gb bulk8 Gbps max software compression20 Gbps TrafficBIG-IP 69002 x Quad core CPU16 10/100/ x 1Gb SFP + 2x 10Gb SFP+2x 320 GB HD (S/W RAID) + 8GB CF16 GB memory58K TPS / 9.6Gb bulk8 Gbps max hardware compression12 Gbps TrafficBIG-IP 39002 x Dual core CPU16 10/100/ x 1Gb SFP2x 320 GB HD (S/W RAID) + 8GB CF8 GB memory25K TPS / 4 Gb bulk5 Gbps max hardware compression6 Gbps TrafficQuad core CPU8 10/100/ x 1Gb SFP1x 300 GB HD + 8GB CF8 GB memory15K TPS / 3.8 Gb bulk3.8 Gbps max software compression4 Gbps TrafficBIG-IP 3600Dual core CPU8 10/100/ x 1Gb SFP1x 160 GB HD + 8GB CF4 GB memory10K TPS / 2 Gb bulk1 Gbps max software compression2 Gbps TrafficBIG-IP 1600Dual core CPU4 10/100/ x 1Gb SFP1x 160GB HD4 GB memory 5K TPS / 1 Gb Bulk1 Gbps max software compression1 Gbps Traffic
23Sizing – Rough Guidelines A single server deployment can handle between 50 to 75 RPS.When scaling out Web Front Ends, assume each one can handle roughly 100 RPS. Assume 85 RPS if Query Search is running on the WFE.According to Microsoft, use the following to determine how many RPS a user will makeLight user, access every 180 secs (20/hr), 1 RPS = 180 active usersTypical user, access every 100 secs (36/hr), 1 RPS = 100 active usersHeavy user, access every 60 secs (60/hr), 1 RPS = 60 active usersExtreme user, access every 30 secs (120/hr), 1 RPS = 30 active usersReferences:
24Sizing Resources Microsoft SharePoint 2007 Development Hoffman, Foster. Sams PublishingPart I dives into some sizing exercisesMicrosoft Office SharePoint Server 2007 Administrator’s CompanionBill English. Microsoft Press.Chapters 2 & 3 discusses sizing in detailMicrosoft TechnetGood information with sizing worksheetsMicrosoft SharePoint Products and Technologies Team BlogJoel Oleson & Mike Watson’s Blog Entries – MS IT Case Study
25Sizing ResourcesHP Sizing and Configuration Tool for Microsoft Office SharePoint Server 2007Plug in various information about user base, and it returns a full suggested hardware packageOne of the most comprehensive sizing guides out there.
26Sizing GuidelinesSizing the SQL cluster for Performance and AvailabilityIs there a strategy to maintaining a certain maximum size to a specific SP database? Should I create separate DB’s or SQL instances for different SP sites?There is a strategy for SP DB implementation, but it has more to do with making administration (i.e. backups & restores) easier than performance.Database ClusteringHigh Availability and Scalability of SQL back end is achieved via SQL clustering technology.No Load Balancer needed.For replication, both data mirroring and log shipping is supported.
27Sizing GuidelinesSizing the SQL cluster for Performance and AvailabilityAs a guideline, what is the recommended number of Web Front Ends to SQL servers?Best PracticesHA Minimum of 2Authenticated Traffic “4:1”*Anonymous Traffic “6:1”*Suggested Limit “8:1”**Database ClusteringHigh Availability and Scalability of SQL back end is achieved via SQL clustering technology.No Load Balancer needed.For replication, both data mirroring and log shipping is supported.*Source**Source
28Sizing vs. Performance Docs 2 Great Resources that compare how sizing affects performanceMicrosoft Office SharePoint Server 2007 on HP ProLiant servers – performance summaryDiscusses when to scale up vs. out (more cores vs. more servers)Plan for performance and capacity (Office SharePoint Server)Discusses acceptable performance limits
29High AvailabilityHealth Monitoring: How does the appliance determine if the servers are up/down?Load Balancing: How does the appliance distribute traffic to the Front Ends?Persistence: Can (and should) the appliance keep a user attached to the same Front End that they initially attached to?
30Multiple Data Center Challenge ClientSite 1Site 2RouterRouterBIG-IP LTMBIG-IP LTMSharePoint Farm SQL DBSharePoint Farm SQL DBCan I deploy SharePoint in Active/Active Redundant DataCenters?
31Multiple DataCenter Challenge RouterBIG-IP LTMSharePoint Farm SQL DBSite 1ClientSharePoint Farm SQL DBSite 2Can SharePoint be deployed with Active/Active Redundant DataCenters?Not in any way supported by Microsoft.Reasoning: SQL replication engine (mirroring/log shipping) just isn’t ready to handle real time replication with concurrent SharePoint user access
32Multiple Data Center Challenge Strategies to replace the Active/Active DeploymentActive/Standby Data CentersSplitting SharePoint Sites, using both Data CentersData Center Multihoming
33Multiple Data Center Challenge RouterBIG-IP LTMSharePoint FarmSite 1 (Active)ClientSharePoint Farm SQL DBSite 2 (Standby)Solution 1: Active/Standby DataCenterAll users sent to DC1, unless it is no longer accessible.Then all users will be sent to mirrored instanced in DC2Good solution, the main drawback is the expense.
34Multiple DataCenter Challenge ClientSolution 2: Multiple SharePoint SitesDC 1 (Active for Site A)(Standby for Site B)DC 2 (Active for site B)(Standy for site A)SharePoint split into multiple sites, each using different SQL instancesSite A uses Data Center 1 as its primary DC, and Data Center 2 as its backupRouterRouterBIG-IP LTMBIG-IP LTMSharePoint FarmSharePoint Farm SQL DBSite A = humanresources.intranet.netSite B = development.intranet.netMultiple Benefits, including no ‘dark fiber’.
35Multiple Data Center Challenge Strategy 3: Multihoming the Data CenterClustered or MirroredSQL DatabaseApplication ServerWeb ServersISP (Link) Load BalancingRouting (BGP) Solution
36Multihoming the Data Center BGP Solution Use 2 or more separate ISPs to peer with each other, creating a single ‘virtual’ ISP link.Benefits:ISP Links share IP space, so DNS caching not an issueDrawbacks:Convergence time can be long.Difficult to fully leverage all available bandwidthWeb ServersApplication ServerClustered or MirroredSQL DatabaseRouting (BGP) Solution
37Multiple Data Center Challenge ISP Load BalancingMultiple ISP links are used.DNS used to direct users in via ISP1, ISP2, ISP3, etc..Benefits:Performance based usage of ISP linksBetter Bandwidth UtilizationDrawbacks:DNS cachingWeb ServersApplication ServerClustered or MirroredSQL DatabaseISP (Link) Load Balancing
38PerformanceProblem: How Can The Content Be Delivered To The End User In The Most Efficient Way Possible?Combination of Technologies
39SSL Acceleration SSL/TLS Encrypted Clear Text HTTP SSL Connections to a server can eat up as much as 30% of available CPU cycles.SSL on NT/IIS means up to 37x fewer connections/secondSSL Acceleration Devices typically have specialized ASIC processors for terminating SSL.SharePoint officially supports SSL offloadingSSL/TLSEncryptedClear TextHTTP* Source: Networkshop Scaling eCommerce Infrastructure
40Control Bandwidth Usage The F5 SolutionBusiness BenefitControl bandwidth usage and spendingMinimize impact on business-critical applicationsGet more bandwidth from the same size pipeControl traffic spikesRate Shaping + iRules - Bandwidth management to prioritize high-priority applications over P2P traffic and other low-priority applicationsPacket Filtering - Selective filtering of P2P sites based on protocol, addresses, and/or portsKaZaa &Video ConferencingOracleHTTP Traffic4x3x2x1xClientThe Rate Shaping Module allows for per-application, per-protocol and per-user basis to help determine what’s actually on the network and how it is behaving and affecting other traffic. Based on this information, administrators can classify, queue, shape, and rate-control traffic with policies to ensure better application response time for priority traffic, by eliminating bandwidth congestion and competition for their priority applications.The Rate Shaping module:Ensures that critical applications are not impacted by non-priority trafficDelivers optimal application performance by allocating more bandwidth for higher priority applicationsEliminates special purpose Rate Shaping products for simplified, centralized traffic management capabilitiesProvides flexible bandwidth limits, bandwidth borrowing, and traffic queuingControls rate classes based on any traffic variableEnables application bandwidth to be shared across similar priority applications for better resource sharingEnsures that specific types of application traffic stay within authorized boundariesAt a high level, the Rate Shaping feature allows for traffic limiting, prioritization and borrowing, for maintaining enough bandwidth and fast service for high priority applications and traffic.BIG-IP users can define traffic and application limits, control the rate at which those resources are allowed to spike or burst, provide queuing to prioritize traffic types, and define relationships where certain traffic types can borrow from other traffic types.Control per application, per protocol, per user40
41Fast Cache Unmatched Flexibility Provides Superior Application Offloading Intelligent memory based cacheFull support for static and dynamic contentExclusive “Multi-Store” caching for prioritized application serviceSuperior caching of pre-compressed contentMost advanced cache controls - iRules41
42HP / F5 Joint SharePoint 2007 Best Practices & Deployment Guide Joint performance testing to determine best practices for accelerating SharePoint 2007 & 2010Over 100 separate tests ran & recorded, with varying network conditions, such as latency, packet loss, & bandwidthWhitepaper (results) posted:
43HP ResultsInternet – asymmetric BIG-IP LTM with WebAccelerator solutionWhile not able to provide all the capabilities and benefits of a symmetric solution, results show that deploying a single BIG-IP LTM with WebAccelerator appliance in this scenario will have measurable benefits in terms of increased throughput and in providing users with an improved experience.• Typical throughput improvements for the 6Mbps and 1536Kbps tests approached a factor of 2 (double the throughput). Again, it was not possible to emulate sufficient load for the 44Mbps tests to drive the accelerated WAN to capacity, but the trends are similar to the 6Mbps tests and the same degree of improvement should be expected.• The hits-per-page ratio dropped from 3:1 (un-accelerated) to about 1.2:1 (accelerated) showing a good degree of protocol optimization.• Average page (response) times showed improvements ranging from factors of between 3 and 5 (that is, some functions took one fifth of the time).• Client LAN traffic was reduced to 75% of the un-accelerated cases.• A good level of compression was achieved, but note that the users’ browsers are used to un-compress the data and need to be set to do so.
44Branch Office Scenario Results Average time for a Document Open decreased 12xAverage time for a Page Open decreased by over 6x
45Internet Scenario Results Average Page Open Time decreased by over 60%Average Search Time decreased by over 40%
46Questions to ask ANY vendor Give me your SharePoint StoryWhat testing have you done with SharePoint?What SharePoint specific development efforts have you undertaken?
47Questions to ask ANY vendor How do you determine server availability and health?What’s the recommended method of distributing traffic?What methods does the appliance have for persisting users?
48F5 Resources F5 SharePoint 2010 Deployment Guide HP F5 SharePoint Acceleration DocF5 Microsoft Business Development TeamJeff Bellamy–Business Development Director for the Microsoft Partnership – –Ryan Korock – Senior Solutions Architect – –James Hendergart – Business Development Manager – –Helen Johnson – Solutions Engineer – –