Slow clone transfer speed on Windows Server 2008
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products will end after February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Git clones are slow due to lower transfer speeds (typically less than 200 KB/s), especially on higher latency connections.
- Windows Server 2008
- The clone speed can be tested outside of Bitbucket Server by using
git daemonto host the repository with the Git protocol. The same clone speed should be seen this way as well.
- If Git pushes are slow, it's also possible to be running into Git push operations extremely slow on Windows
The slow clones are caused by the size of the TCP packets being limited to 9,000 bytes or below. This is likely due to the architectural behavior of the Windows Socket API in Windows Server 2008. More details on this can be found at Slow performance occurs when you copy data to a TCP server by using a Windows Sockets API program.
Clone speeds can be improved by using the blocking Java connector and adjusting the socketBuffer in Tomcat. In
$BITBUCKET_HOME/shared/server.xml make the following changes:
- Change the protocol to
- Add the
This workaround will not be viable in Bitbucket Server 5.0+ due to the blocking connector being removed from Tomcat 8.5.
Upgrade to Windows Server 2012 or migrate to Linux, see Migrating Bitbucket Data Center to another server for details.
Linux is the recommended option for larger instances.