How do you scale Bitbucket Server?
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on 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
The type of hardware you require to run Bitbucket Server depends on a number of factors:
The number and frequency of clone operations. Cloning a repository is one of the most demanding operations. One major source of clone operations is continuous integration. When your CI builds involve multiple parallel stages, Bitbucket Server will be asked to perform multiple clones concurrently, putting significant load on your system.
The size of your repositories. On large repositories, many operations require more memory and more CPUs.
The number of users.
See our guide Scaling Bitbucket Server for sizing guidelines based on the 3 factors above.
Was this helpful?