Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,666
Community Members
 
Community Events
176
Community Groups

Run garbage collection

My repository "alive" is touching 3.6 GB on bitbucket, I deleted several files on it using git filter-repo (as recommended by the git project.) Despite pushing the same, size has not reduced, in fact it increased from 3.0 to 3.6GB. On pushing the local cleaned repo to a new remote (aka alive_reduced) the size is down to 200 MB. It is urgent that garbage collection be run server side. I have rewound head and pushed to trigger it automatically (Dangling commits enabled in Labs) but to no avail.

It would be great if the support team could run gc server side.

Regards.

 

1 answer

1 accepted

0 votes
Answer accepted

Hi @Aarushi Mehta,

I ran a git gc on this repo and its size is 873.1 MB now.

You mentioned that the local cleaned repo is 200 MB. Does this local repo have all branches that the remote does?

Could you try taking a mirror clone of the repo with the command

git clone --mirror <repo_url>

then run the command git count-objects -Hv inside that mirror clone, and let me know what is the output?

The following

I have rewound head and pushed to trigger it automatically (Dangling commits enabled in Labs) but to no avail.

will trigger a garbage collection only if the repo is over the 4 GB limit, which explains why it wasn't triggered for your repo.

We have a feature request to allow users to trigger a git gc for their remote repos:

If you'd be interested in that, I would suggest adding your vote in the feature request (by selecting the Vote for this issue link) as the number of votes helps the development team and product managers better understand the demand for new features. You are more than welcome to leave any feedback, and you can also add yourself as a watcher (by selecting the Start watching this issue link) if you'd like to get notified via email on updates.

Kind regards,
Theodora

Thank you for addressing this and your explanation!

git count-objects -Hv gives me:
count: 0
size: 0 bytes
in-pack: 11466
packs: 1
size-pack: 234.25 MiB
prune-packable: 0
garbage: 0
size-garbage: 0 bytes

It is not as high priority as we ended moving to another repo! Thank you. I have voted on said issue as well

Regards

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events