Git gc Request - Remote Repository Size does not Match will local?
Asked by Lalit Karole:

I have this repositories on my workspace, I have perform required steps to reduce the size of this repository and Able to successfully reduce size but the updated size does not show under Repository Size. Need to Run garbage Collection.  
this is URL for repo's :-  
\[REDACTED URL\]  
\[REDACTED URL\]

I have Also Mailed Support Team on this Email :- support@bitbucket.org


Answers:
author: Ben
body: Hi Lalit,

I have further censored the URLs you've shared to avoid any identifiable repository/workspace information being presented here.

<br />

I've successfully run garbage collection against both repositories in the backend to clear up any dangling commits contributing to the size difference.

The first repo reduced from **491MB to 132MB** and the second reduced from **2.2GB to 92MB.**   

Would it be possible for you to check it on your end and see if that has helped?  

We want to inform you that we do have a [Feature request](https://jira.atlassian.com/browse/BCLOUD-11610) to provide users with the option to limit the file size that is able to be pushed to GIT to prevent such issues from occurring again.

<br />

Our Dev team is currently working on implementing the feature request and we don't have any ETA for its implementation. I would suggest you **"Watch"** this ticket for future updates from our Dev team.  

Cheers!

- Ben (Bitbucket Cloud Support)

comments: author: Lalit Karole
body: Thank you Ben for Providing Support regarding this, I can see Updated Size Reflected On my Side also. I want to know How can I run this from My side on remote repos or trigger the garbage collection process when i needed. so it would be very helpful.


author: Ben
body: Hi [@Lalit Karole](/t5/user/viewprofilepage/user-id/5317812)

Unfortunately, this is not possible from the user side.

Our team has done a lot of work in the background to trigger GC for the repository based on heuristic repository settings (configured in the backend) that are safe for the platform and for the objects that are being cleaned up by the GC process. Additionally, measures have been put in place to prevent users from being blocked from pushing.  
Please refer to this blog post to learn more:

* <https://bitbucket.org/blog/updated-repository-limits-and-automatic-garbage-collection>

Essentially, this process is automated and once certain garbage thresholds are reached this will be run in the backend. If more immediate garbage collection is required, this can be requested either in a support or community ticket.

Cheers!

- Ben (Bitbucket Cloud Support)


author: Lalit Karole
body: Yes I am Understanding That it not possible to run garbage collection from user side due to various reasons, however would it be possible to trigger this process somehow when needed.

And while you are here. Can You Please run gc on this also - ++~~\[URL redacted\]~~++ this repo of mine need urgent gc


author: Ben
body: Hi Lalit,

Unfortunately not at this stage - there was a feature request ticket to allow this from the user end logged with our developers that has since been closed, you can view the rationale behind it being closed by viewing the comments on the ticket here:

* <https://jira.atlassian.com/browse/BCLOUD-11593>

Cheers!

- Ben (Bitbucket Cloud Support)


author: Ben
body: [@Lalit Karole](/t5/user/viewprofilepage/user-id/5317812)

For the other gc request, unfortunately, you will need to log a new community support ticket using a profile that is associated with that workspace. The email address that you have used to log this community question is not a member of that workspace.

For security reasons, we are unable to perform actions against any repository unless it has been raised by a user that belongs to that workspace.

Cheers!

- Ben (Bitbucket Cloud Support)


author: Lalit Karole
body: I have Also Posted question from that account Please execute same on that. username is \[REDACTED\]


author: Ben
body: Hi [@Lalit Karole](/t5/user/viewprofilepage/user-id/5317812)

Just saw that community ticket now, I've responded there :)


Tags: atl-rvw

bitbucket-cloud

cloud