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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


bithucket server high cpu high memory

The bitbucket service is unavailable, high cpu and high memory appear, and it is found that git pack-objects occupies a lot of memory and cpu resources. This problem happens occasionally, is there any solution?



2 answers

1 vote
Fabio Racobaldo _Herzum_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 13, 2022

Hi @klin111 ,

there are many aspects that could impact your bitbucket performances. Please read the following article that could help you in order to increase performances.

Hope this helps,


Thanks, I have read this official article and it doesn't seem to solve my problem. git cpu memory high problem. Do you have any other articles to recommend?

Same for me, I've followed the resources doc and configured the server to represent a large instance of Bitbucket and it still crashes regularly.

no update on this issue? we are facing similar issue with several git pack objects taking all the systems memory and leading to OOM errors in linux

I was able to get it resolved on my end. Our build server, Team City, was connecting to Bitbucket so frequently, I believe each project was connecting every 30 seconds looking for code changes that it was taking up most of the resources. To resolve the issue, we setup webhooks between Team City and Bitbucket so that a build would run only when code was committed, instead of each project checking every 30 seconds. 


Hope this helps

Thanks Mark. Something similar on our end. We had end users uploading big files which were being processed by git consuming so much memory and cpu and having the rest of processes waiting until collapse of the system. 

More control on what users are uploading to certain projects solved the issue.


Thx for your reply!

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events