SharePoint 2013 Performance Enhancements
5 likes8,856 views
The document discusses performance enhancements for SharePoint 2013, focusing on real-time application monitoring, event management, and operational health metrics. It highlights benefits like reduced troubleshooting time by 30%, improved user satisfaction, and better resource management. Recommendations for cache configuration and management practices are also provided to optimize SharePoint infrastructure.
SharePoint 2013 Performance Enhancements
- 1. SharePoint 2013 Performance Enhancements
- 2. Sponsored by: Real-time application monitoring, event management, and operational health metrics for Microsoft SharePoint Reduce troubleshooting time by up to 30% Increase efficiency and improve user satisfaction Avoid downtime and costly outages Meet or exceed service level agreements Maximize investment in current infrastructure Visit us on the web at www.binarywave.com
- 5. Build To Suit Make the Network Work for You The Database Is King Squeeze Those Bits Cache In Look Good But Perform Better
- 8. Deployment size Small farm Medium farm Large farm Total number of users < 10,000 < 100,000 < 500,000 Recommended cache size 1 GB for the Distributed Cache (Default 10% RAM) service 2.5 GB (Manual adjustment) 12 GB (Limit of16GB per server) Total memory allocation for the Distributed Cache 2 GB service (double the (Memory size must recommended cache size match in all servers) above) 5 GB 24 GB (32GB Max Limit) Recommended architectural configuration Dedicated server Dedicated server 1 1 Dedicated server or colocated on a front-end server Minimum cache hosts per 1 farm
- 10. SP aware rule based traffic shaping Throttling Routing Prioritization Load Balancing
- 12. Throttling Rules Machine Pool Routing Target Static Weight Health Weight Routing Target Static Weight Health Weight Execution Group Routing Rule Routing Rule Routing Rule Routing Rule
- 13. Throttling Rules Rule 1 Rule 2 Rule 3 Execution Group 1 Execution Group 0 Rule 1 Rule 2 Rule 5 Rule 3 Rule 6 Execution Group 3 Rule 7 Rule 8 Machine Pool 1 Machine Pool 2 Server 1 Server 4 Server 2 Server 3 Server 5 Server 6 Rule 9 Rule 0
- 14. Counter name Description Connections Current The total number of connections that are currently open by Request Manager. Connections Reused / Sec Routed Requests / Sec The number of connections per second that are reused when the same client connection makes another request without closing the connection. The number of routed requests per second. The instance determines the application pool and server for which this counter tracks. Throttled Requests / Sec The number of throttled requests per second. Failed Requests / Sec The number of failed requests per second. Average Processing Time Last Ping Latency Connection Endpoints Current Routed Requests Current The time to process the request that is, the time to evaluate all the rules and determine a routing target. The last ping latency (that is, Request Manager's PING feature) and the instance determine which application pool and machine target. The total number of endpoints that are connected for all active connections. The number of unfinished routed requests. The instance determines which application pool and machine target.
- 19. First Request Page 1 First Request Page 1 Controls Download Manager Controls Chrome Content Page 2 Content Second Request Page 2 Controls Chrome Content Controls Download Manager Second Request Chrome Chrome Content
- 21. 29 Requests / 570KB 21 Requests / 321KB
- 23. Sponsored by: Real-time application monitoring, event management, and operational health metrics for Microsoft SharePoint Reduce troubleshooting time by up to 30% Increase efficiency and improve user satisfaction Avoid downtime and costly outages Meet or exceed service level agreements Maximize investment in current infrastructure Visit us on the web at www.binarywave.com