Jira Server sizing guide

Still need help?

The Atlassian Community is here for you.

Ask the community

The sizing and hardware recommendations on this page were originally created for Jira 6.3. If you need updated sizing guidance for Jira 7.0 and up, see Jira Data Center size profiles.

Sizing Recommendations

The following table lists sizing recommendations for Jira instances based on your average use cases and hardware demands. The specific recommendations for your company depend on the specific growth type, intensity and use cases. We recommend that you collaborate with one of our Experts to receive a specific recommendation. If you're interested for a referral for a partner/expert, please contact us.

In addition, if you find that you are running in the upper limits of the enterprise scale recommendations, please check out Jira Data Center. It's specifically designed to help large organizations expand their Jira solution as their performance and sizing demands increase.

Recommendations for sizing

Sizing Legend Small-scale Mid-scale Large-scale Enterprise scale
Application usage
Users 100 500 2000 10000
Active (Concurrent) Users 25 200 600 2000
Issues 15000 60000 200000 1000000
Issues/month 200 1000 4000 20000
Custom Fields 50 150 300 600
Permission Schemes 3 15 25 100
Projects 20 80 200 300
Parent Issue Types 10 20 50 160
Resolutions 10 20 30 40
Priorities 10 15 25 40
Workflows 5 20 35 100
System level small scale medium scale large scale enterprise scale
System Requirements
Description For this low level server, consider a dual core type CPU and fast, physical hard disks. For a medium level machine, consider using a medium server CPU (e.g. quad core) and high speed hard disks (e.g. 7200RPM+) for the home directory and backups. For a high-level system, we recommend using high processing power (e.g. dual quad core or higher) and ensuring high I/O performance, e.g. through the use of 10,000+ RPM or Solid State Disks. This should be a top of the line server with enterprise grade processing power (e.g. 6 quad cores or more) and the highest possible I/O performance (e.g. Raid 10, Solid State Disks).
System Memory 8GB > 8GB > 16GB >128GB
JVM Heap Size > 1GB > 2GB > 4GB Consult our experts
App Install Dir ~200MB ~200MB ~200MB ~500MB
Backups > 100MB > 200MB 1-5GB 10GB
Attachments 10 - 50GB 50-100GB 100GB 400GB
Application Logs 25MB 50MB 100MB 250MB
Total disk space 10 - 50 GB 50 - 100 GB 100-200 GB > 500 GB

Staying ahead of hardware demand

Below are a few best practices for sizing a Jira deployment for your organization. The goal of this section is to help provide generic sizing information as a starting point for what memory, hard disk space and a few other configuration settings are required for deploying Jira.

Category General Recommendation Jira
Java Version Atlassian products like Jira can show significant differences in performance depending on the Java version it is installed on.

For Jira 7.0 and hIgher Oracle Java 1.8 is recommended.  Starting with Jira 7.13.1 and higher, Jira started supporting AdoptOpenJDK version 8 as well. 

More details in How to run Jira Server on AdoptOpenJDK.

Disk Space The disk space recommended generally depends on the size of your instance and the anticipated growth. It is recommendable to dedicate more disk space to the respective directories than specified as minimum requirements. For the examples to the right, general instances sizes have been defined

Installation Directory: 20GB
Home Directory: 50-200GB
Indexes: Use fastest disks possible (7200RPM+ disk speed or use Solid State Drives)
Attachments: 50GB+ NAS/SAN

Memory In general, there is a difference between the general memory of the server that an Atlassian application is installed and the JAVA HEAP size dedicated to the application. See table above
Last modified on Aug 7, 2019

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.