We installed a Bitbucket server in intention to migrate from our current GitBlit server.
However, when executing git push to local large repositories (~15GB) we experience an unexpected slowness in Bitbucket in comparison to the same git push command in GitBlit.
Upload rate for Bitbucket server - ~2.5MB
Upload rate for GitBlit server - ~10MB
Both servers are identical in resources (CPU/MEM) and networking means. Both websites are configured to use HTTPS and certificate is signed with our organization's CA.
Server logs didn't reveal any relevant information.
I would appreciate your input and suggestions for this issue!
The first items to check are the resources of the server (CPU / MEM) against the Supported Platforms.
Also, the Git version (on the server and on the clients) will be an important factor to consider.
If you are running Bitbucket Server on Windows, have a look at the Git push operations extremely slow on Windows page as well.
Thanks for the response.
I followed to Supported Platforms page when I first created/installed the server, and I see memory is not fully utilized when performing the push operation.
I installed the newest git version on both the linux server and windows client (from which I run push operation).
Also, the bitbucket process on the linux server is run by by atlbitbucket local user, defined as suggested.
Do you have any more ideas?
I would recommend raising a ticket with the Atlassian Support (https://support.atlassian.com/contact/) so that our team can review all details of the installation and provide an analysis.
The team will also need the Git local client log and a Support Zip:
Enable debug and profiling log
Administrator>>Support>>Logging and profiling and click to check/enable "Enable debug logging" and "Enable profiling"
Enable Git debug log (client side)
Turn Debug logging on for Git locally on Linux
Turn Debug logging on for Git locally on Windows
I' ve got a very similar problem under Centos with Bitbucket Server 5.3.1. Things like clone etc. work as expected, but pushing is like 10 times slower than expected. The CPU is going from idle to 99% for the time of pushing. The problem does occur not only for large repos, but also for newly created ones.
I'm open for any ideas, as I couldn't get infos out from the logs.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot