Versions
- 9.3
- 9.2
- 9.1
- 9.0
- 8.19
- 8.18
- 8.17
- 8.16
- 8.15
- 8.14
- 8.13
- 8.12
- 8.11
- 8.10
- 8.9
- 8.8
- 8.7
- 8.6
- 8.5
- 8.4
- 8.3
- 8.2
- 8.1
- 8.0
- 7.21
- 7.20
- 7.18
- 7.19
- 7.17
- 7.16
- 7.15
- 7.14
- 7.13
- 7.12
- 7.11
- 7.10
- 7.9
- 7.8
- 7.7
- 7.6
- 7.5
- 7.4
- 7.3
- 7.2
- 7.1
- 7.0
- 6.10
- 6.9
- 6.8
- 6.7
- 6.6
- 6.5
- 6.4
- 6.3
- 6.2
- 6.1
- 6.0
- 5.16
- 5.15
- 5.14
- 5.13
- 5.12
- 5.11
- 5.10
- 5.9
- 5.8
- 5.7
- 5.6
- 5.5
- 5.4
- 5.3
- 5.2
- 5.1
- 5.0
- See all
Bitbucket Server production server data
Scaling Bitbucket Server
On this page
Related content
- No related content found
This page provides some data around the Bitbucket Server production instance that we run internally at Atlassian. We're providing this to give some idea of how Bitbucket Server performs in a production environment. Please realise that this information is entirely specific to this particular instance – the details of your own installation may result in different performance data.
This data was collected with New Relic in February 2013, when the server was running a pre-release version of Bitbucket Server 2.2.
On this page:
Hardware
The performance data below was gathered from the Atlassian Bitbucket Server production server running on:
- Virtualized hardware
- 4 Hyper-threaded cores
- 12 GB RAM
Load
Load data summary for February 2013:
| Type | Load |
|---|---|
| CPU usage | less than 30% on average |
| Load average | less than 3 on average |
| Physical Memory | peaked at 31% |
| Processes | Git: 17.3% CPU Java: 18.8% CPU |
| Clones | on average less than 300ms |
| Git operations/hour | peaking at 11,000 with an average of about 3,500 |
| Concurrent connections/hour | peaking at 100 connections with an average of about 40 concurrent connections |
| CI running against Bitbucket Server instance | 3 build servers with approximately 300 agents |
Server load
Git operations
Git clone operations
Git operations per hour
Git operations per hour (stacked)
Concurrent connections per hour
Git operations - cache hit/miss
Git operations - cache hit/miss
Git protocol usage per hour
Related content
- No related content found