GC Request / Size Limit Increase Request

[Robert Lehmann]

Hi team,

Could you please run GC on our <name_redacted> repo?

No matter how many commits I revert, I cant get it below the 4 gb again, so GC is never triggering... 

In general we are quite close to the 4GB, so we would be happy if a size limit increase would be possible too.

Thank you very much.

[Theodora Boudale]

Hi Robert and welcome to the community!

I ran a git gc on your repository but its size remains unchanged at 4 GB.

Can you please do the following:

1. Create a mirror clone of this repo with the command

git clone --mirror <repo_url>

2. Then, navigate to the directory of the mirror clone and run

git count-objects -Hv

What output do you get from this last command?

This is to understand if 4 GB is the size of the core Git repo, or if perhaps the core repo size is less and PR refs may contribute to the size.

The default max size for a repository is 4GB. We can only override this limit on request, up to 10 GB, for customers on the Premium plan.

Just a head up, I removed the repo name from your post to protect your privacy.

Kind regards,
Theodora

[Robert Lehmann]

Hey Theodora,

thanks for the quick response!

I did as you asked. The result of 'git count-objects -Hv' is:

count: 0
size: 0 bytes
in-pack: 94644
packs: 1
size-pack: 3.57 GiB
prune-packable: 0
garbage: 0
size-garbage: 0 bytes

[Theodora Boudale]

Thank you for the output, Robert.

Since the size of the pack is 3.57 GiB, I suspect that the other 430 MB might be PR refs that reference deleted objects. If that is the case, the only way to remove these PR refs would be by deleting the PRs. Is this something you would be willing to consider? I will need to create a support ticket on your behalf if you would like to explore this option, so a colleague of mine can check and provide you with a list of PRs that contribute to the repo's size.

Even if we delete the PRs though, the repo's size is very close to the limit. Do you have large and/or binary files in the repo? If so, I would recommend rewriting the repo's history to either remove such files that do not need to be versioned, or move them to LFS if you need to version them. Otherwise, the repo's size may reach 4 GB soon, even after PR deletion.

You can check this post of mine in a different question with more details:

• https://community.atlassian.com/t5/Bitbucket-questions/Revert-bitbucket-repository-state-to-one-day-prior/qaq-p/1908360#M76762

Please feel free to let me know if you have any questions and how you would like us to proceed.

Kind regards,
Theodora

[Robert Lehmann]

Hey Theodora,

I would like to get the PRs deleted for now. Afterwards, once the repo is working again, I will clean it up more by squeezing history together, etc. (as the raw assets of the repo are just 2.5 gb).

[Theodora Boudale]

Hi Robert,

I created a support ticket on your behalf. You should have received an email with a link to the ticket. You should also be able to view the ticket here (after you log in):

• https://support.atlassian.com/requests/

I added an internal summary of what we have discussed, so that the colleague of mine who assigns the ticket can provide you with a list of the larger PRs and ask for confirmation on the deletion.

Please feel free to let me know if you have any questions.

Kind regards,
Theodora

[Robert Lehmann]

@Andy Heinzer Can you please help? :)