nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Need to run garbage collection on the repository

ValdikSS

Hello, I just received "Your workspace is over 1 GB" email, which states that I need to clean my workspace to continue using free plan.

My repository <redacted> updates the information twice a day, using Pipelines, rewriting the history. Its size is no more than 50 MB, however the repository statistics page states it's occupying 1.7 GB of workspace size.

Please run GC on this repository, and tell what could be done to trigger the GC automatically in the future.

Accepted answers

Theodora Boudale

Hi @ValdikSS and welcome to the community!

I ran a git gc on the repo and its size has been reduced. Does it look ok now on your end?

A git gc is triggered automatically on every push, but with different parameters every time depending on many different conditions. If the automated one doesn't reduce your repo size, you can create a question in community and either myself or one of my colleagues will run a git gc manually that will optimize the repo size better.

Just a heads up, I edited the repo URL for privacy reasons.

Kind regards,
Theodora

All comments

Mikael Sandberg

Hi @ValdikSS,

Welcome to Atlassian Community!

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

Theodora Boudale

Hi @ValdikSS and welcome to the community!

I ran a git gc on the repo and its size has been reduced. Does it look ok now on your end?

Just a heads up, I edited the repo URL for privacy reasons.

Kind regards,
Theodora

ValdikSS

Thanks, that worked!

ValdikSS

1 month later, the repository is 591.82 MB again.

@Theodora Boudale @Mikael Sandberg is anything could be done?

Syahrul

Hey @ValdikSS

Please allow me to chip in. I have manually triggered GC to reduce the repository size.

There are several reasons why a repository's size may increase. Generally, if you have recently made numerous changes or added new items to the repository (being active), this can lead to an increase in size over time due to the accumulation of blob and tree objects. Running garbage collection (GC) can help clean this up. Hope this helps.

Regards,
Syahrul

ValdikSS

Yes, I understand.

I have a CI pipeline which runs daily on schedule, and updates the files in the repository by rewriting the top commit and force-pushing. Over the course of month, the repo could become 500+ MB.

For some reason, in this scenario Bitbucket does not run git gc, at least not that frequently.

Could you tune anything from your side, or should I write here every month to run the gc manually?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud