5 ms·

I got the email several weeks ago - and I still don’t fully understand what it means! Unbelievable confusion. PLEASE can someone in plain english say what the

I got the email several weeks ago - and I still don’t fully understand what it means! Unbelievable confusion. PLEASE can someone in plain english say what the limits are PER REPOSITORY? Is it 5GB per repository? can you have as many repositories as you want? I don’t care or use namespaces.

Macha 4y ago
If you're a paying user it's 5GB per repository. If you are not on a paid tier, all your repositories share a pool of 5GB per namespace. A namespace is basically a user or project. So if you don't use namespaces, everything is under your personal user namespace and your limit is 5GB total storage across all your repositories.
- Donckele 4y ago
  So can I create multiple “namespaces” and each one can contain a repository of 5GB?
  - Macha 4y ago
    They need to be top level groups. But yes, if you have public repos repoa/repoa and repob/repob instead of user/repoa and user/repob, then my understanding is both repoa and repob will hae 5GB each.
- mlegendre 4y ago
  > If you're a paying user it's 5GB per repository. TFA says 10 GB (and so does my experience). > A namespace is basically a user or project I believe you meant to write "a user or a group".
john_cogs 4y ago
Apologies for the confusion. I'd be happy to provide some more clarity. The answer depends on which tier of GitLab you are using. If you are using the free tier on GitLab SaaS, there will be a 5GB storage limit per top-level namespace. Paid tiers on GitLab SaaS will have limits of 50GB for Premium and 250GB for Ultimate. Community programs (GitLab for Open Source, GitLab for Education, and GitLab for Startups) will have the same 250GB limit as the Ultimate tier. Self-managed users have no limit.
- Donckele 4y ago
  Thanks. 2 more questions: - Do I have to do anything now with all my “top-level” repositories (total >5GB)? - When I create a new repository do I have to do something else as well (create new namespace)?
  - john_cogs 4y ago
    The FAQ contains information on how to manage your storage which will be helpful for top-level namespace exceeding 5GB in storage: https://about.gitlab.com/pricing/faq-efficient-free-tier/#managing-your-storage-usage https://about.gitlab.com/pricing/faq-efficient-free-tier/#ma...
- arinlen 4y ago
  > If you are using the free tier on GitLab SaaS, there will be a 5GB storage limit per top-level namespace. What does this cover? Does it cover the size of a git repo? Build artifacts, both temporary and exported to packages? And what about Docker images? Docker images concern me the most. It's terribly easy to build and use Docker images that are >100MB, and 50 of those easily go beyond 5GB. Two projects with nightly builds easily go beyond that in a month even when doing nothing at all.
  - dnsmichi 4y ago
    > What does this cover? https://about.gitlab.com/pricing/faq-efficient-free-tier/#managing-your-storage-usage https://about.gitlab.com/pricing/faq-efficient-free-tier/#ma... provides a list of what counts towards the storage limits, and also ways to manage, reduce and cleanup storage. > Does it cover the size of a git repo? Build artifacts, both temporary and exported to packages? And what about Docker images? Yes, they all are storage types that add to the overall storage consumption. > Docker images concern me the most. It's terribly easy to build and use Docker images that are >100MB, and 50 of those easily go beyond 5GB. Two projects with nightly builds easily go beyond that in a month even when doing nothing at all. You can define container cleanup policies within the registry, matching on age, tags, etc. https://docs.gitlab.com/ee/user/packages/container_registry/reduce_container_registry_storage.html#cleanup-policy https://docs.gitlab.com/ee/user/packages/container_registry/...

Macha 4y ago

If you're a paying user it's 5GB per repository. If you are not on a paid tier, all your repositories share a pool of 5GB per namespace. A namespace is basically a user or project. So if you don't use namespaces, everything is under your personal user namespace and your limit is 5GB total storage across all your repositories.

Donckele 4y ago
So can I create multiple “namespaces” and each one can contain a repository of 5GB?
- Macha 4y ago
  They need to be top level groups. But yes, if you have public repos repoa/repoa and repob/repob instead of user/repoa and user/repob, then my understanding is both repoa and repob will hae 5GB each.
mlegendre 4y ago
> If you're a paying user it's 5GB per repository. TFA says 10 GB (and so does my experience). > A namespace is basically a user or project I believe you meant to write "a user or a group".

john_cogs 4y ago

Apologies for the confusion. I'd be happy to provide some more clarity. The answer depends on which tier of GitLab you are using. If you are using the free tier on GitLab SaaS, there will be a 5GB storage limit per top-level namespace. Paid tiers on GitLab SaaS will have limits of 50GB for Premium and 250GB for Ultimate. Community programs (GitLab for Open Source, GitLab for Education, and GitLab for Startups) will have the same 250GB limit as the Ultimate tier. Self-managed users have no limit.

Donckele 4y ago
Thanks. 2 more questions: - Do I have to do anything now with all my “top-level” repositories (total >5GB)? - When I create a new repository do I have to do something else as well (create new namespace)?
- john_cogs 4y ago
  The FAQ contains information on how to manage your storage which will be helpful for top-level namespace exceeding 5GB in storage: https://about.gitlab.com/pricing/faq-efficient-free-tier/#managing-your-storage-usage https://about.gitlab.com/pricing/faq-efficient-free-tier/#ma...
arinlen 4y ago
> If you are using the free tier on GitLab SaaS, there will be a 5GB storage limit per top-level namespace. What does this cover? Does it cover the size of a git repo? Build artifacts, both temporary and exported to packages? And what about Docker images? Docker images concern me the most. It's terribly easy to build and use Docker images that are >100MB, and 50 of those easily go beyond 5GB. Two projects with nightly builds easily go beyond that in a month even when doing nothing at all.
- dnsmichi 4y ago
  > What does this cover? https://about.gitlab.com/pricing/faq-efficient-free-tier/#managing-your-storage-usage https://about.gitlab.com/pricing/faq-efficient-free-tier/#ma... provides a list of what counts towards the storage limits, and also ways to manage, reduce and cleanup storage. > Does it cover the size of a git repo? Build artifacts, both temporary and exported to packages? And what about Docker images? Yes, they all are storage types that add to the overall storage consumption. > Docker images concern me the most. It's terribly easy to build and use Docker images that are >100MB, and 50 of those easily go beyond 5GB. Two projects with nightly builds easily go beyond that in a month even when doing nothing at all. You can define container cleanup policies within the registry, matching on age, tags, etc. https://docs.gitlab.com/ee/user/packages/container_registry/reduce_container_registry_storage.html#cleanup-policy https://docs.gitlab.com/ee/user/packages/container_registry/...