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. The Old Rules Still Apply
Build
To
Suit
Exciting new is but regret
it you will if old rules are
forgotten.
Make the
Network
Work for
You
The
Database
Is
King
Squeeze
Those
Bits
Cache
In
Look
Good But
Perform
Better
10. Distributed Cache Guidelines
Deployment size
Small farm
Medium farm
Large farm
Total number of users
< 10,000
< 100,000
< 500,000
Recommended cache
size for the Distributed
Cache service
1 GB
(Default 10% RAM)
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
match in all servers)
size above)
5 GB
24 GB
(32GB Max Limit)
Recommended
architectural
configuration
Dedicated server or colocated on a front-end
server
Dedicated server
Dedicated server
Minimum cache hosts
per farm
1
1
1
12. Request Management
SP aware rule based
traffic shaping
Seek not too much data
or throttled you will be.
Throttling
Routing
Prioritization
Load
Balancing
14. Request Management Components
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
15. Request Management Rules
Throttling Rules
Rule
1
Rule
2
Rule
3
Execution Group 1
Execution Group 0
Rule
1
Rule
2
Rule
5
Rule
3
Machine Pool 1
Server
1
Server
2
Server
3
Rule
6
Execution Group 3
Rule
7
Rule
8
Machine Pool 2
Server
4
Server
5
Server
6
Rule
9
Rule
0
16. Request Management Counters
Counter name
Connections Current
Connections Reused / Sec
Routed Requests / Sec
Throttled Requests / Sec
Failed Requests / Sec
Average Processing Time
Last Ping Latency
Connection Endpoints Current
Routed Requests Current
Description
The total number of connections that are
currently open by Request Manager.
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.
The number of throttled requests per second.
The number of failed requests per second.
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.
25. 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