Require gc on remote repo after using BFG Repo-Cleaner

[tim-bbav]

Hi, I received a warning that my repo was well above the new 1GB limit, so I ran BFG Repo-Cleaner which reduced the local repo size from over 2GB to under 700MB.

However, upon a full push to the remote I see that the size has not reduced (in fact, it may have gone up).

It looks like a full gc needs to be run on the repo. Can somebody at Atlassian please run this for me?

Many thanks

[Ben · Accepted solution]

Hi @tim-bbav 

Often times garbage is accumulated as a result of cleanup operations - this is either removed by an automated garbage collection process (only executes once a certain threshhold is met) or via manual execution on the server-end by Atlassian staff.

I've just executed a gc which reduced the repo size from 3GB > 700MB.

Your workspace is currently consuming 989MB which is close to the 1000GB limit which will be active on 28th April. I'd suggest shrinking other repositories if possible.

Cheers!

- Ben (Bitbucket Cloud Support)

[tim-bbav]

Hi @Ben 

Thank you for that!

I have just shrinked the lightbox-3-installer repo and did even more shrinking on the lightbox-3 repo (having outsourced the largest files). This should have saved a couple more hundred MB. Would you mind running GC again please?

[Tansu Akdeniz]

Hi @tim-bbav 

Welcome to the community!

I notified the Atlassian support team here. They will reach out to you!