You are on page 1of 14

# Servers Workloads

Web
Servers
and DB Intranet
1 Servers Collaboration

Web Content
2 All Management

Application
Servers Managed
3 (MMS) Metadata

Web Video
4 Server Streaming

Query
5 Servers eDiscovery

1 All Servers All


Web
2 Servers All

3 All Servers All

4 All Servers All

5 All Servers All


Distributed
Cache
6 Servers All

Distributed
Cache
7 Servers All

Search
8 Servers Search

Internet Sites
9 All and Search

Search
10 Servers Search

Search
11 Servers Search

Search
12 Servers Search
Workflow
Manager
13 Server All

14 All All

Office Web
Apps
15 Server OWA
Guidance Reference
GUIDANCE BASED ON TEST RESULTS AND RECOMMENDATIONS

- Server Specs: With 4 cores, 12 GB RAM web servers (virtual) and 1 16 core DB, 32 GB
RAM
'- RPS/server - you can expect more than 40 RPS per server for green zone and more
than 70 RPS for red zone
'- 1 DB server was able to scale upto 10 web servers Estimate performance and capacity r

Provides results for two types of sites: sites using new features: cross-site publishing
along with Content Search web part and managed navigation, sites using classical
feature: author-in publishing, content query web part and structured navigation.
Cross site publishing: Server specs - 16 cores, 24 GB RAM (physical), topology - 3
WFE+Query,1 Crawler, 1 App, 1 DB,
Cross site publishing results 78 page views/sec (with 3 WFEs)
Author-in-place publishing results 57 page views/sec (1 WFE) Estimate capacity and performance f

As its difficult to translate end user requests to MMS requests, the results provided
here are with respect to MMS server response time and VSTS tests completed. Roughly,
you can assume number of tests completed same as requests hitting MMS for sizing your
MMS servers. Estimate capacity and performance f

1 server (VM, 4 cores, 12 GB RAM) was able to provide acceptable streaming


experience up to 400 concurrent users.
Dataset was about 350 videos, size range 1 MB 1 GB (total 14 GB)
Video stored in SharePoint content db with BLOB cache enabled Estimate capacity and performance f

Doesnt provide detailed tests, but provides information on how compliance, and
eDiscovery can effect capacity and performance in SharePoint Server 2013
eDiscovery queries can increase query latencies that users observe by as much as 100
percent. If you run close to capacity for your user search queries, you might consider
running eDiscovery queries and exports during non-peak hours to have a smaller effect
on user search queries Estimate capacity and performance f

GENERAL RESOURCES

Minimum hardware specification for each type of server Hardware and software requirement
A Web server typically supports 10,000-20,000 users.
For 90,000 users this architecture starts with six Web servers to serve user requests and
leaves room for additional Web servers, if needed.

Two-three Web servers that are dedicated for search crawling is a good starting point,
depending on rates of change and freshness requirements. Enterprise-scale farms for SharePoin

It doesnt provide any specific guidance on number or specifications of server. It provides


the following two things:
1. Recommended Topologies based on number of users: < 100, <1000, <10,000, > 10,000
2. Reference Topology for Microsoft Office Division farm that had following workload and
dataset:

15,000 users
2,500 unique users per hour
1.7 million requests per day
1.3 Terabytes total data Streamlined topologies for SharePoin

Generic guidance on how to scale farms as covered in the Streamlined topologies visio SPC192 - SharePoint 2013 Performan

As in Streamlined topologies, this diagram also provides generic guidance, and also
provide some statements about specific numbers as provided below:
1. The number of users will affect the requirement for web servers. Factor 10,000 users
per web server as a starting point. Adjust the number based on how heavily the servers
are utilized. Heavy use of client services will increase the load on web servers.
2. Start with two application servers dedicated to the query processing component and
index partitions and place all other service application components on a separate
application server. Based on utilization, consider either adding all-purpose application
servers that are configured similarly, or adding application servers to dedicate resources
to specific service applications.
3. The query role can be combined with the Web server role on a server only if there are
enough resources. Running both of these roles on a single virtual machine requires a 6-
8-core VM and a physical host that runs Windows Server 2012. A 4-core VM does not
provide enough resources for both the query processing component and the Web server
role.
4. A detailed table for number of servers for each search component, based on number
of items. this is covered in more detail in Enterprise Search diagram. Traditional topologies for SharePoint
The diagram does not provide any information on number of Cache servers, but provides
the following information about the memory of cache server e.g.

The memory allocation for the cache size must be between 8GB and 16GB, and the
memory allocation of the cache size must be less than or equal to 40% of the total
memory on the server. Plan and use the Distributed Cache s

This provides little more details about minmum number of cache host servers based on
number of total users. Also there's recommendation, upto 10,000 users, you can go with
colocated DC servers, beyond that you should go with dedicated server (minimum
number 1) Plan for feeds and the Distributed Ca

The Search has very detailed description on sizing, which covers lot of things for different
number of items (10m, 40m, 100m) such as: RAM, DISK, CPU, Number of Servers. Enterprise search architectures for S

It does not provide per role or per component guidance, but provides one topology with
predefined performance:

A medium Internet sites (FIS) topology is optimized for a corpus size of 3,400,000 items,
processing approximately 100-200 documents per second, depending on language, and a
usage pattern of 85 page views per second, which corresponds to 100 queries per
second. Internet sites search architectures fo

The article covers the details provided in two search visio diagrams Scale search for performance and av

Provides very detailed information on each search components, which isn't available in
the two visios. It also includes important information on IOPS requirements for search Capacity Planning, Sizing and High Av

Most detailed information on every aspect of sizing for enterprise scenarios SPC 172 - Capacity Planning, Sizing a
Minimum three servers are required to provide high availability for Workflow Manager Configuring a Highly Available Workfl

For SharePoint 2013 virtual environments, dynamic memory is NOT supported:

We do not support this option for virtual machines that run in a SharePoint 2013
environment. The reason is that this implementation of dynamic memory does not work
with every SharePoint feature. For example, Distributed Cache and Search do not resize
their caches when the allocated memory for a virtual machine is dynamically changed.
This can cause performance degradation, especially when assigned memory is reduced. Use best practice configurations for t

Based on our performance tests, an Office Web Apps Server, togetherwith two Intel Xeon
processors (8 cores), 8 GB of RAM, and a 60 GB hard disk, should support up to 10,000
users where most of the usage is viewing. A server that has a 16 core CPU and 16 GB of
Ram should support up to 20,000 users. These results will vary, depending on usage
patterns and other factors such as network hardware. Plan Office Web Apps Server
Type Remarks

There are many more details in the


article. Also it provides comparison of
performance of 2010 vs 2013

Interestingly, there wasnt any


TechNet application server in this farm, so there
Article isn't any guidance on that

There are very important findings and


TechNet useful guidance in the article that you
Article must go through

TechNet
Article

TechNet
Article

TechNet
Article

Provides minimum guidance, but this


minim should NOT be considered as
TechNet recommended. For which, you need to
Article refer to other resources
Use this guidance just a thumb rule, as
Visio no supporting test data has been
diagram provided here

Most of this guidance is from SharePoint


Conference session "SPC192 - SharePoint
Visio 2013 Performance and Capacity
diagram Management"

If you dont have access to the session


recording, refer to streamlined
SPC topologies visio, as most of information
Session covered in this session is available there

Along with sizing, this diagram is a good


Visio reference for topology design principles
diagram explained with example topologies.
Visio
diagram

TechNet
article

This diagram covers Search from Intranet


perspective. The internet search is
Visio different and covered in the other
diagram diagram

In the associated document


(http://technet.microsoft.com/en-
us/library/jj219628.aspx) its
recommended to use physical servers:

We recommend that you deploy search


Visio topologies for Internet sites on physical
diagram hardware.

TechNet
Article

This information is taken from


SharePoint Conference 2012 session -
TechNet SPC172 (Barry Waldbaum and Olaf
Wiki Birkeland)

If you dont have access to the session


recording, refer to the TechNet Wiki and
enterprise search vision, as most of
SPC information covered in this session is
Session available there
It's because it depends on Windows
TechNet Server Service Bus, which requires three
Article servers for HA

TechNet
Article

TechNet
Article
Version Number Date
1.0 6-Apr-13

2.0 9-Apr-13
3.0 15-Apr-13
4.0 9-May-13
Changes
First Draft
1. Added RESOURCES BASED ON TEST RESULTS AND RECOMMENDATIONS (Row# 3)
2. Added additional resource for distributed cache (Row# 7)
Added links for WCM and MMS tests
Added links for Video streaming and eDiscovery tests, provided summary of test results

You might also like