Jira Server System Requirements RAM CPU and Disk Explained
Jira installed fine but crawls in daily use? Nine times out of ten the machine was sized by hope. Here is what Jira actually consumes, and the cheap upgrades that change everything.
✍️ Technical Anshu🪟 Windows⏱️ 6 minute read
🎥 Watch the install first — this guide helps you pick the machine it deserves
Atlassian publishes minimums; minimums describe what starts, not what a team can work on. This guide gives the practical numbers behind the install video — memory first, because that is where Jira lives.
A small-team Jira machine — honest sizing (example)
RAM total8 GB min
Free for Jira~4 GB
Disk typeSSD
Users in this example10 to 25 people, one small team
DatabaseExternal — see the database guide
👆 Example sizing for one small team, not an Atlassian guarantee. The pattern matters more than the numbers: Jira competes with Windows itself for memory, and loses on slow disks.
1
Why Jira Feels Heavy — It Is a Java Application
Jira runs on the Java platform with its own built-in Tomcat web server. That gives it power and plugins, but it also means Jira keeps a large memory workspace (the Java heap) permanently occupied, indexes your issues on disk, and does real work every time someone opens a busy board. On a machine sized for file sharing, Jira will feel slow — and users will blame Jira, not the hardware.
2
RAM — the Honest Numbers
Evaluation on a spare PC: 4 GB total RAM will install and run for one or two learners. It will not be pleasant.
Small team (up to roughly 25 users): give the machine 8 GB or more, so Windows, the database and Jira each get breathing room. If the database lives on the same box, lean towards more.
Growing teams: watch actual usage in Administration → System info instead of guessing. Boards with hundreds of issues and many plugins are what push memory up — user count alone is a weak predictor.
Practical rule: if the server regularly uses its page file while people work, Jira will stutter no matter what else you tune.
3
CPU, Disk and the Silent Killer
CPU: a modern quad-core is comfortable for a small team. Jira is rarely CPU-bound at this size.
Disk: use an SSD. Jira's home directory holds attachments, search indexes and logs, and it reads and writes constantly. A spinning hard disk is the single most common reason a "powerful" server feels dead.
Space: the program itself is small; attachments are not. A helpdesk attaching screenshots daily can grow the home directory by gigabytes a month. Plan space for growth and for backups of that same data.
4
The Machine Itself
A dedicated machine that stays on — a laptop that sleeps at night is not a server, whatever its specs.
A static IP address on your network, so the team always finds Jira at the same place.
Windows Server is the natural home for production; Windows 10 or 11 is fine for labs and evaluation.
🎥 Watch the Complete Install in the Video
The full installation, screen by screen, is in the video — this page is your written companion for every step and warning.
It installs and runs for evaluation with one or two users, but boards and searches will feel slow. For any real team, 8 GB total with about half free for Jira and its database is the honest starting point.
Does Jira need a graphics card or special hardware?
No. Jira is a web application — CPU, RAM and fast disk are all that matter. The biggest real-world upgrade is moving the home directory and database onto an SSD.
Should the database be on the same machine?
For a small team, yes — same machine is simpler and works well if RAM is sufficient. Larger instances split the database onto its own server. Either way, use a supported external database for production, not the built-in evaluation one.
This guide is based on the Technical Anshu Jira Server installation video • Stuck on any step? Ask in the video comments — you will get a reply there 🙏