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; } } }

I would kindly request support runs gc on my repos

steve_dyq0bn

Hello,

I've recently used bfg to remove large files from my repo (in two sessions) but it has increased in size both times.

Initial size 218.52 MB

1st run size increased to 426.2 MB

2nd run size increased to 629.76 MB

I'm not sure if this is the correct place to make the request but I would kindly request support runs gc on my repos.

thank you.

Accepted answers

Ben

Hi @steve

It's actually expected for a repo to increase in size after performing maintenance operations, as it creates garbage that needs to be cleaned from our side with a server-side garbage collection.

I executed a gc and this reduced the size from 629MB to 203MB.

You had a much larger repo at 2.9GB that I've also executed a gc against - this reduced down to 1.1GB.

Overall - your workspace is still using over 3GB - if your aim is to reduce the size < 1GB I'd suggest finding any large binary files using the below command and following documentation to remove/convert these files to GIT LFS:

git rev-list --objects --all \
| git cat-file --batch-check='%(objecttype) %(objectname) %(objectsize) %(rest)' \
| awk '/^blob/ {print substr($0,6)}' \
| sort -r --numeric-sort --key=2 \
| numfmt --field=2 --to=iec-i --suffix=B --padding=7 --round=nearest

Once you've done so, please let me know and I'll perform subsequent gc's (just give me the repo filesize rather than sharing the name as this is a public forum).

Alternatively, you can upgrade to our Standard/Premium plans which offer unlimited workspace size:

https://www.atlassian.com/software/bitbucket/pricing

Cheers!

- Ben (Bitbucket Cloud Support)

All comments

Brant Schroeder

@steve welcome to the Atlassian community

I have escalated to Atlassian support.

Ben

Hi @steve

It's actually expected for a repo to increase in size after performing maintenance operations, as it creates garbage that needs to be cleaned from our side with a server-side garbage collection.

I executed a gc and this reduced the size from 629MB to 203MB.

You had a much larger repo at 2.9GB that I've also executed a gc against - this reduced down to 1.1GB.

Once you've done so, please let me know and I'll perform subsequent gc's (just give me the repo filesize rather than sharing the name as this is a public forum).