Garbage collection / Repo size reduction

[robert_tutic]

Hello, I have a repository which has bloated in size (2.9GB) due to big pushes made on non-merged branches.

I've done some cleanup and now the total repo size is <100 MB. However, this isn't reflected on the repository size. I guess references are stored a bit longer there and I'm not sure how long they will persist.

To clarify: doing a clean clone is in fact now cloning only <100 MB (down from 2.9GB), and that is nice and well. The only issue is that on repository side I still have the warning of repository size being 2.9GB, close to the 4 GB limit.

From what I've gathered, garbage collection can be run server-side to clean up dangling objects - can you help with that?

[Ben · Accepted solution]

Hi @robert_tutic 

To troubleshoot this further, we'll need access to your workspace and the repository in question. Our system requires us to have a formal support ticket to do this.

I can see you have a Premium workspace and are therefore entitled to support directly from our support team. Please raise a support ticket, and include the repository name within this ticket so that we may assist you further:

• http://support.atlassian.com/contact/

If you encounter issues raising a ticket, please let me know your timezone so we may raise one on your behalf with the team who operates within your region.

Cheers!

- Ben (Bitbucket Cloud Support)

[robert_tutic]

Thanks, in the meantime it seems that automatic garbage collection has run, so in fact no more support is necessary~

[Mikael Sandberg]

Hi @robert_tutic,

Welcome to Atlassian Community!

I have notified the Atlassian support team that is on here and they will get back to you within 2 business days to get this resolved.