Description

The following tables describes the Azure Resource types and sizes that are provisioned with each of the Sitecore ARM templates found in the Sitecore Azure Quickstart Templates repository on GitHub. The "0" topologies are not supported for production sites, they are purely for development and test exercises.

The sizes were determined by performance testing a simple marketing site and finding the smallest resource sizes required to hit the associated visits per month. The simple marketing site was mainly read-only, no login activity, and minimal xDB interactions. Dependent requests were not tested (that is, images, JS, CSS) and it is assumed these assets will be served up by a CDN.

The sizes and instance counts below serve as a starting point for you when trying to figure out the Azure requirements for your site. You should expect to have to adjust some or all of the sizes or instance counts once you have performance tested your application.

Experience Management (XM)

	Performance Rating
Component	xM1 Extra Small	xM2 Small	xM3 Medium	xM4 Large	xM5 Extra Large
Approximate visits per month range	0 - 100,000	100,000 - 200,000	200,000 - 1,000,000	1,000,000 - 5,000,000	5,000,000 - 10,000,000
Content Management Server – Azure Web App	1 x B2	1 x B2	1 x B2	1 x B2	1 x B2
Content Delivery Server – Azure Web App	1 x B2	2 x B2	3 x B2	4 x S3	8 x S3
Core Database – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1
Master Database – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1
Web Database – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S2	1 x S3
Search – Azure Search [1]	1 x S1 (1 RS x 1 P)	1 x S1 (1 RS x 1 P)	1 x S1 (1 RS x 1 P)	1 x S1 (1 RS x 1 P)	1 x S1 (1 RS x 1 P)
Monitoring – Azure App Insights	1 x Basic	1 x Basic	1 x Basic	1 x Enterprise	1 x Enterprise
Session State – RedisCache	1 x C1	1 x C1	1 x C1	1 x C1	1 x C1

Experience Platform (XP)

	Performance Rating
Component	xP0 Single	xP1 Extra Small	xP2 Small	xP3 Medium	xP4 Large	xP5 Extra Large
Approximate visits per month range	-	0 - 100,000	100,000 - 200,000	200,000 - 1,000,000	1,000,000 - 5,000,000	5,000,000-10,000,000
Content Management Server – Azure Web App	1 x S1	1 x B2	1 x B2	1 x B2	1 x B2	1 x B2
Content Delivery Server – Azure Web App	-	1 x B2	2 x B2	3 x B2	4 x S3	8 x S3
xDB Processing Service – Azure Web App	-	1 x B1	1 x B1	1 x B1	1 x B2	1 x B2
xDB Reporting Service – Azure Web App	-	1 x B1	1 x B1	1 x B2	1 x B2	1 x B2
Core Database – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1
Master Database – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1
Web Database – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S1	1 x S2	1 x S3
Reporting Database – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S2	1 x S2	1 x S2
Search – Azure Search [1]	1 x S1 (1 RS x 1 P)	1 x S1 (1 RS x 1 P)	1 x S1 (1 RS x 1 P)	2 x S1 (1 RS x 2 P)	3 x S1 (1 RS x 3 P)	3 x S1 (1 RS x 3 P)
Monitoring – Azure App Insights	1 x Basic	1 x Basic	1 x Basic	1 x Basic	1 x Enterprise	1 x Enterprise
Session State – RedisCache	1 x C1	1 x C1	1 x C1	1 x C1	1 x C1	1 x C1

Experience Database (XDB)

	Performance Rating
Component	xDB1 Extra Small	xDB2 Small	xDB3 Medium	xDB4 Large	xDB5 Extra Large
Approximate visits per month range	0 - 100,000	100,000 - 200,000	200,000 - 1,000,000	1,000,000 - 5,000,000	5,000,000 - 10,000,000
xDB Processing Service – Azure Web App	1 x B1	1 x B1	1 x B1	1 x B2	1 x B2
xDB Reporting Service – Azure Web App	1 x B1	1 x B1	1 x B2	1 x B2	1 x B2
Core Database – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1
Master Database – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1
Web Database – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S2	1 x S3
Reporting Database – SQL Azure	1 x S1	1 x S1	1 x S2	1 x S2	1 x S2
Search – Azure Search [1]	1 x S1 (1 RS x 1 P)	1 x S1 (1 RS x 1 P)	2 x S1 (1 RS x 2 P)	3 x S1 (1 RS x 3 P)	3 x S1 (1 RS x 3 P)
Monitoring – Azure App Insights	1 x Basic	1 x Basic	1 x Basic	1 x Enterprise	1 x Enterprise

Notes

• [1] Azure Search size refers to Search Unit (SU), which is the product of replica and partitions used by the Azure Search service (RS X P = SU). At a minimum, every service starts with 1 SU (one replica multiplied by one partition). See search units and SU combinations for more information.
  As a cost saving measure, the ARM Templates initially set up with only 1 partition, and you can then add new partitions as  you require. However, from a budgeting point of view you should expect to increase to the number of partitions listed by the end of the first year.