Blob storage performance reference

Abstract

See the performance specifications for blob providers and migration scripts to configure the best solution for your requirements.

Some of your considerations for using Azure Blob Storage are: how to configure the best solution for your needs and to identify your blob storage performance requirements. Refer to the following blob provider and migration script performance tables to configure a solution that best suits your requirements.

Blob providers performance

The following configurations are benchmarks of Azure storage blob providers and SQL Database blob providers.

Note

The tests were carried out on a dedicated VM in South East Asia.

Table 4. System configuration

O/S

Windows 10 Redstone 1 [1607 Anniversary update] (10.0.14393.3025)

CPU

  • Intel Xeon CPU E5-2650 v2 2.60GHz

  • 2 CPUs

  • 2 Logical cores

  • 2 Physical cores

Host

  • .NET Framework 4.6.1 (CLR 4.030319.42000)

  • 64 bit



Table 5. General configuration

XP Scaled

  • Size: Extra small, Small, Medium, and Large

  • Region: South East Asia

SQL

  • Master: S1

  • Web: S1, and S2

Storage account

  • Type: Block blob storage

  • Performance tier: Standard

  • Storage account type: Blob storage

  • Redundancy: RA-GRS

  • Access tiers: Cool, and hot



Migration scripts performance

Refer to the following table for the performance of the migration scripts during testing:

Table 6. Migration scripts performance

Sitecore installation

Environment where script ran

Blobs

Size

Time

CPU

Memory

Sitecore on-premise

Local box

660

~ 15.7GB

44 minutes

15%

78%

Sitecore on Azure

Kudu

683

~ 16GB

86 minutes

5.66%

4.5%

Sitecore on Azure

Local box

683

~ 16GB

105 minutes

8%

58%

Sitecore on Azure

Azure Cloud Shell

683

~ 16GB

78 minutes

-

-



The Azure Storage blob provider and migration scripts automatically handle transient errors and fail fast when errors persist. If a transient (temporary) error in communication over the network occurs while you are uploading blobs to Azure Storage, the Azure Storage blob provider and the migration scripts will automatically retry a few times before reporting a failure. However, if you need to revert for some reason, you can run a revert migration script.

Refer to the following table for the performance of the revert migration scripts during testing:

Table 7. Revert migration scripts performance

Sitecore installation

Environment where script ran

Blobs

Size

Time

CPU

Memory

Sitecore on-premise

Local box

660

~ 15.7GB

44 minutes

-

-

Sitecore on Azure

Kudu

672

~ 15.7GB

86 minutes

-

-

Sitecore on Azure

Local box

672

~ 15.7GB

105 minutes

-

-

Sitecore on Azure

Azure Cloud Shell

672

~ 15.7GB

78 minutes

-

-