Skip to content

Latest commit

 

History

History
39 lines (31 loc) · 1.86 KB

container-registry-limits.md

File metadata and controls

39 lines (31 loc) · 1.86 KB
title description services author ms.service ms.topic ms.date ms.author ms.custom
include file
include file
container-registry
dlepow
container-registry
include
08/30/2018
danlep
include file

| Resource | Basic | Standard | Premium | |---|---|---|---|---| | Storage1 | 10 GiB | 100 GiB| 500 GiB | | Max image layer size | 20 GiB | 20 GiB | 50 GiB | | ReadOps per minute2, 3 | 1,000 | 3,000 | 10,000 | | WriteOps per minute2, 4 | 100 | 500 | 2,000 | | Download bandwidth MBps2 | 30 | 60 | 100 | | Upload bandwidth MBps2 | 10 | 20 | 50 | | Webhooks | 2 | 10 | 100 | | Geo-replication | N/A | N/A | Supported | | Content trust (preview) | N/A | N/A | Supported |

1 The specified storage limits are the amount of included storage for each tier. You're charged an additional daily rate per GiB for image storage above these limits. For rate information, see Container Registry pricing.

2 ReadOps, WriteOps, and Bandwidth are minimum estimates. ACR strives to improve performance as usage requires.

3 docker pull translates to multiple read operations based on the number of layers in the image, plus the manifest retrieval.

4 docker push translates to multiple write operations, based on the number of layers that must be pushed. A docker push includes ReadOps to retrieve a manifest for an existing image.