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
Small-scale
- 100 users
- 25 active concurrent users
- 15,000 total issues
- 200 issues/month
- 50 custom fields
- 3 permission schemes
- 20 projects
- 10 parent issue types
- 10 resolutions
- 10 priorities
- 5 workflows
Mid-scale
- 500 users
- 200 active concurrent users
- 60,000 total issues
- 1,000 issues/month
- 150 custom fields
- 15 permission schemes
- 80 projects
- 20 parent issue types
- 20 resolutions
- 15 priorities
- 20 workflows
Large-scale
- 2,000 users
- 600 active concurrent users
- 200,000 total issues
- 4,000 issues/month
- 300 custom fields
- 25 permission schemes
- 200 projects
- 50 parent issue types
- 30 resolutions
- 25 priorities
- 35 workflows
Enterprise-scale
- 10,000 users
- 2,000 active concurrent users
- 1,000,000 total issues
- 20,000 issues/month
- 600 custom fields
- 100 permission schemes
- 300 projects
- 160 parent issue types
- 40 resolutions
- 40 priorities
- 100 workflows
Recommendations for sizing
Small-scale: For this low level server, consider a dual core type CPU and fast, physical hard disks.
- System Memory – 8GB
- JVM Heap Size > 1GB
- App Install Dir – 200MB
- Backups >100MB
- Attachments – 10-50GB
- Application Logs – 25MB
- Total disk space – 10-50GB
Mid-scale: 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.
- System Memory > 8GB
- JVM Heap Size > 2GB
- App Install Dir – 200MB
- Backups >200MB
- Attachments – 50-100GB
- Application Logs – 50MB
- Total disk space – 50-100GB
Large-scale: 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.
- System Memory > 16GB
- JVM Heap Size > 4GB
- App Install Dir – 200MB
- Backups >1-5GB
- Attachments – 100GB
- Application Logs – 100MB
- Total disk space – 100-200GB
Enterprise-scale: 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 – 128GB
- JVM Heap Size > Consult our experts
- App Install Dir – 500MB
- Backups >10GB
- Attachments – 400GB
- Application Logs – 250MB
- Total disk space > 500GB
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.
Java Version: Atlassian products like Jira can show significant differences in performance depending on the Java version it is installed on.
- For Jira 5.1 Java SE 6 Update 24 or higher; 1.6_24 through 1.6_45; or 1.7 is recommended
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
For the latest recommendations, visit here.