Azure-devops-docs: Limits

[Materia-xx]

Can you throw in a note about the max size of a single published artifact, and the max size of all stored artifacts in an account or explicitly state that both of these things do not have size limits. If that info is on another page, add a link ? I did find another limits page about package artifacts, but not sure that is the same thing that this page is talking about? Clarification on that too would be neat.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 7175ebdc-0bba-7e00-d113-036a5cffe5fa
• Version Independent ID: 149ab9f4-0b7d-97e7-6cf5-1b54fd04c63c
• Content: Publish and consume build artifacts in builds - Azure Pipelines & TFS
• Content Source: docs/pipelines/artifacts/build-artifacts.md
• Product: devops
• GitHub Login: @andyjlewis
• Microsoft Alias: alewis

[elbatk]

@mitchdenny do you know these size limits? It may good to add them.

@Materia-xx I think you may be referring to this limits page.

[elbatk]

Actually, does this issue help you, @Materia-xx : https://github.com/MicrosoftDocs/vsts-docs/issues/1400?

It looks like there are no hard limits set. However, I do believe that the newer Pipeline Artifacts perform much, much more efficiently with larger file sizes than Build Artifacts.

[mitchdenny]

We've tested Universal Packages and Pipeline Artifacts up to 4TB (per artifact). We stopped testing at that point because we figured most usages above that are on the extreme side.

In terms of total size per Organization, we don't have a hard limit. Theoretically the scale unit that hosts an organization as the aggregate content volume across all orgs approaches 500PB but that assumes a fairly even key distribution.

Our largest Organization stores north of 61PB (that is an internal team).

[elbatk]

Thanks Mitch! I hope this helps ya out @Materia-xx , going to close this issue, but if you have more questions feel free to reach out!