Multiple problems with new workspace size limit on free tier

[faber75]

As of today Bitbucket started severely limiting workspace size in free plans, summing up all the repositories to a limit of 1Gb, which having some projects with lot of commits is a very low cumulative limit.
Also removing the option to download seems to me pretty rough.

However, it's a good occasion to clean up some trash, so i did, removing some older projects and erasing the history of a projects that i still need online, but where keeping track of all changes is no more relevant.

Counting roughly the bytes from bitbucket interface i should have cleared at least 1Gb.

Yet, on plan details i see no changes on the storage used; i understand that the value won't be always fresh, but 24 hours has passed and i still see no changes.
Also, even before deleting al those repositories, the added up size was far lower than the one calculated in plan settings, about 20-30% lower.
I only use repositories, no large files, no pipelines.

Also, checking the plan and pricing page https://www.atlassian.com/software/bitbucket/pricing 

i see no reference to the new limits, and what limit i may have moving to a standard user profile.

Thanks for your time.

[Theodora Boudale · Accepted solution]

Hi everyone,

Thank you for reaching out.

After deletion of your repositories, please allow up to 30 days for the background cleanup job to run and total workspace size to be re-adjusted.

Please note that the size enforcement will take place on April 28, 2025, until that date your workspace is not going to be impacted by the new limits. The new size will be reflected within 30 days of repository deletion.

Our team is working on improving the cleanup time and it is planned to be implemented prior to limits enforcement changes taking place.

Also, even before deleting al those repositories, the added up size was far lower than the one calculated in plan settings, about 20-30% lower.

@faber75 Could you please let me know you calculated that the added up size was lower then the one in plan settings?

If you rewrote/erased history for a repo, it may take some time for dangling commits to be removed from the repo. If you want, I can run a git gc for the repos where you did that, so that the dangling/unreferenced commits are removed now.

If you'd like me to do that, please provide the repo names masked (i.e. replace some letters in the repo names with asterisks) and I can run a git gc for those.

I will reach out to my team internally regarding the info on the page https://www.atlassian.com/software/bitbucket/pricing.

For Standard and Premium plans:

• There will be no total storage limit applied to a workspace.
  
  
• It will be possible to upload additional files to the Downloads page of a repo.
  
  
• Workspace snippets will be available.
  
  
• Starting 25th April 2025, logs for Pipelines builds on Standard and Premium plans will be retained for 400 days:
  
  https://community.atlassian.com/t5/Pipelines-articles/Upcoming-changes-to-Bitbucket-Pipelines-Logs-retention-policy/ba-p/2858027

Kind regards,
Theodora

[faber75]

Hi Theodora,

thanks for the update for for your kind offer to run gc, the problem is keeping track of what i've cleaned and what not, and the impact i had on the limit.

About how i think i occupy a smaller size than the one listed in workspace settings: i went in every single repository, went in repository details and added the size listed there.

I use no other service that takes space that i know of, no large files, no pipelines.

Sincerely, 90 days to react to a change so big it a limited times, having a counter updated every 30 days is... very very bad service for those having to endure this new limit.

Still, your product, your rules; and being a free user for so long i understand doesn't give me much weight on your decisions.
I'll evaluate passing to a standard subscription.

[Theodora Boudale]

Hi @faber75,

I understand that not seeing the change in size immediately makes it more difficult to keep track of the impact. Just to clarify, the counter doesn't get updated every 30 days. It is the background cleanup job for deleted repos that can take up to 30 days to run, and as such, any deleted repos that haven't been cleaned up still count towards the workspace size. I have forwarded your feedback to my team and we are working to improve this.

I manually checked and added the size of each repository under your personal workspace (including the deleted ones that haven't been cleaned up yet) and the sum of these sizes matches what Bitbucket reports as your workspace size at the moment. I'm not sure how you came up with a different number. Some sizes were in KB while others were in MB, so I don't know if that contributed to a miscalculation.

My offer for running a gc still stands, so you can always reach out at a later time if you'd like me to do it.

Kind regards,
Theodora

[faber75]

Hi Theodora,

thanks for taking the time to check my stats. 

I double checked the sums i did before writing my question but probabily i've done some error, not counting something that i already cleard; not being able to see what i changed and what not for days can put you in such troubles.

Thanks for forwarding my request to the dev team; having to clean up, gc, remove old branches and not being able to see the result for weeks is really troublesome.

having the counter updated at least once a day would be ideal to understand the situation. i've cleared most of what i could in the last days, but the counter is still stuck to the original value i read on tuesday, 4 days ago.

Btw, thanks for your offer to gc for me, since i cleared a bunch of projects and also totally deleted many others, at least for this first 'round' i'll wait the automatic update, i fear would miss some name and don't want to waste your time.

Best regards,

Fabrizio

[Theodora Boudale]

Thank you for the feedback Fabrizio and I certainly understand what you're saying.

The counter doesn't show updated info at the moment for the deleted repos specifically, because it can take up to 30 days for the deleted repos to be completely removed from our system.

When it comes to the garbage collection (because of deleted branches, rewritten history), a git gc runs on every push, but with different parameters depending on many different conditions. Changes in size because of a git gc should be reflected in real time, however, not all dangling commits may have been removed with the git gc because that depends on the parameters the git gc run with. The one I can run manually would optimize the repos better.

You are more than welcome to ask for a git gc at any time.

Kind regards,
Theodora

[Hrtz]

The same here - I've removed old repositories and cleaned a lot of space but workspace storage used size stayed the same. I thought after 24 hours it will be updated, but nothing...

I hope they will address this in time.

[mscarchilli]

30 days for the site to update math? So I just transferred a handful or repos to clean up space, and I was going by the number your site was giving me. When things didn't make sense I did the math myself, and I am within the limits.

So because your site doesn't update for up to 30 days (ridiculous), I just transferred repos I didn't necessarily need to because your site was giving false information, and now I (as well as other people using them) will have to deal with updating all of my local repos with the new remote origins, and in turn wasting even more of my time. Thanks.

Do better Atlassian. One example... make a note that the size can take up to 30 days to be updated when viewing that number, which would save people wasted time.