Stash is now known as Bitbucket Server.
See the

Unknown macro: {spacejump}

of this page, or visit the Bitbucket Server documentation home page.

This page provides some data around the Stash production instance that we run internally at Atlassian. We're providing this to give some idea of how Stash 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 Stash 2.2.

On this page:

Hardware

The performance data below was gathered from the Atlassian Stash production server running on:

  • Virtualised hardware
  • 4 Hyper-threaded cores
  • 12 GB RAM

Load

Load data summary for February 2013:

TypeLoad 
CPU usageless than 30% on average
Load averageless than 3 on average
Physical Memorypeaked at 31%
Processes

Git: 17.3% CPU

Java: 18.8% CPU

Clones

on average less than 300ms

Git operations/hourpeaking at 11,000 with an average of about 3,500
Concurrent connections/hourpeaking at 100 connections with an average of about 40 concurrent connections
CI running against Stash server

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

  • No labels
 

 

 

 

 Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.