Description

The following tables describe the Azure resource types and sizes that are provisioned with the Sitecore XC 9.0.2 ARM templates found in the Sitecore Azure Quickstart Templates repository on GitHub.

The performance rating sizes were determined by performance testing the Sitecore Experience Accelerator Storefront site and finding the smallest Azure Resource sizes required to achieve the associated visits per month below. Dependent requests (for example, images, JS, CSS) were not included as part of the test as it is assumed these assets will be served by a CDN. Live event detection was also not enabled as part of the testing, so you might require larger sizes if you enable this feature of the Experience Platform.

The ratio of test cases run during the load testing were 5% for checkout, 15% for category browsing, 30% for product browsing, and 50% for home page browsing.

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

Please be aware that Sitecore does not provide ARM Templates for ASEv2 at this time, but if you plan to update the existing ARM templates in ASEv2, all App Services must be isolated sizes.

Experience Commerce (XC)

	Performance rating
Component	Single	Extra small	Small	Medium	Large	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
Approximate orders per hour	-	-	535	801	2606	-
Content Management server – Azure Web App [2]	-	-	1 x S3	1 x P3v2	1 x P3v2	-
BizFx – Azure Web App
Id Server – Azure Web App
Content Delivery server Azure Web App		-	1 x S3	1 x P3v2	4 x P3v2	-
xDB Processing service – Azure Web App		-	1 x S1	1 x S1	1 x S2	-
Cortext Processing service – Azure Web App		-	1 x S1	1 x S3	2 x S3	-
xDB Reporting service – Azure Web App		-	1 x S1	1 x S1	1 x S2	-
Cortext Reporting Service – Azure Web App		-	1 x S1	1 x S2	1 x S3	-
Marketing Operations – Azure Web App	-	-	1 x S1	1 x S2	1 x S3	-
Marketing Automation reporting – Azure Web App
xConnect Collection search – Azure Web App
xConnect Collection – Azure Web App		-	1 x P3v2	1 x P3v2	1 x P3v2	-
xConnect Reference data – Azure Web App
Shops – Azure Web App	-	-	1 x S3	1 x P3v2	2 x P3v2	-
Ops – Azure Web App
Authoring – Azure Web App
Minions – Azure Web App		-	1 x S1	1 x S1	1 x S1	-
Core database – SQL Azure	-	-	1 x S1	1 x S1	1 x S1	-
Master database – SQL Azure	-	-	1 x S1	1 x S1	1 x S1	-
Web database – SQL Azure	-	-	1 x S3	1 x P1	1 x P1	-
Reporting database – SQL Azure	-	-	1 x S1	1 x S2	1 x S2	-
Pools database – SQL Azure	-	-	1 x S0	1 x S1	1 x S1	-
Tasks database – SQL Azure	-	-	1 x S0	1 x S0	1 x S0	-
Forms database – SQL Azure	-	-	1 x S0	1 x S0	1 x S1	-
Messaging Database – SQL Azure	-	-	1 x S0	1 x S0	1 x S0
Cortex processing Tasks database –SQL Azure	-	-	1 x S0	1 x S0	1 x S0
Cortex processing Storage database – SQL Azure	-	-	1 x S1	1 x S1	1 x S3
Marketing Automation database – SQL Azure	-	-	1 x S0	1 x S1	1 x S1	-
Reference data database – SQL Azure	-	-	1 x S1	1 x S2	1 x S3	-
Shard map management – SQL Azure	-	-	1 x S0	1 x S0	1 x S0	-
Shard 0/1 databases – SQL Azure	-	-	2 x S3	2 x P1	2 x P1	-
Global database – SQL Azure	-	-	1 x S0	1 x S0	1 x S0	-
Shared database – SQL Azure	-	-	1 x S3	1 x P1	1 x P1	-
Search – Azure Search [1]	-	-	1 x S1 (1 RS x 1 P)	2 x S1 (1 RS x 2 P)	3 x S1 (1 RS x 3 P)	-
Monitoring – Azure App Insights	-	-	1 x Basic	1 x Basic	1 x Enterprise	-
Session state – RedisCache	-	-	1 x C1	1 x C1	1 x C1	-

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 are initially set up with only 1 partition and then you can add new partitions as required, but from a budgeting point of view you should expect to increase to the number of partitions listed by the end of the first year.