General System Requirements for Confluence

As a general basis, Atlassian’s system requirements for Confluence apply, but the operation of a Linchpin Intranet Suite instance requires more resources. The different applications require different resources depending on their intended use.

These tables can serve as a basis for your own planning.

Multi-node data center operating packages for hosting in Germany or in your infrastructure

Web server

License size (User) 500 1.000 2.000 3.000 4.000 5.000 10.000
CPU 2 2 4 4 6 6 6
RAM 2 GB 2 GB 2 GB 2 GB 2 GB 2 GB 4 GB
Storage 16 GB 16 GB 16 GB 16 GB 16 GB 16 GB 16 GB

Database System (PostgreSQL)

License size (User) 500 1.000 2.000 3.000 4.000 5.000 10.000
CPU 1 2 3 4 5 6 8
RAM 4 GB 6 GB 8 GB 10 GB 12 GB 14 GB 16 GB
Storage 100 GB 100 GB 100 GB 100 GB 100 GB 100 GB 100 GB

Storage for Attachments, Thumbnails and More (NFS)

License size (User) 500 1.000 2.000 3.000 4.000 5.000 10.000
CPU 1 1 1 2 2 2 2
RAM 2 GB 2 GB 2 GB 2 GB 2 GB 4 GB 4 GB
Storage 100 GB 200 GB 300 GB 400 GB 500 GB 600 GB 800 GB

Application server (Jira, Confluence, Bitbucket, Bamboo or Crowd)

License size (User) 500 1.000 2.000 3.000 4.000 5.000 10.000
CPU 2 2 4 6 8 8 10
RAM 16 GB 16 GB 16 GB 20 GB 24 GB 24 GB 32 GB
Storage 50 GB 50 GB 50 GB 50 GB 50 GB 50 GB 50 GB
Quantity 2 2 2 3 3 3 3

Multi-node data center operating packages highly available operation with Amazon Web Services (AWS)

Application server (Jira, Confluence, Bitbucket, Bamboo or Crowd)

License size (User) 500 1.000 2.000 3.000 4.000 5.000 10.000 15.000 20.000
Instance Type r6a.large t3a.xlarge t3a.xlarge t3a.xlarge t3a.2xlarge t3a.2xlarge m6a.2xlarge m6a.2xlarge c6a.4xlarge
Number of Instance Types 2 2 2 2 2 3 3 4 4
CPU 2 4 4 4 8 8 8 8 16
RAM 16 GB 16 GB 16 GB 16 GB 32 GB 32 GB 32 GB 32 GB 32 GB
Storage 150 GB 200 GB 200 GB 200 GB 200 GB 200 GB 200 GB 200 GB 250 GB

Storage for Attachments, Thumbnails and More (NFS)

License size (User) 500 1.000 2.000 3.000 4.000 5.000 10.000 15.000 20.000
Storage 150 GB 200 GB 300 GB 350 GB 400 GB 450 GB 600 GB 800 GB 1.000 GB

Database System (PostgreSQL)

License size (User) 500 1.000 2.000 3.000 4.000 5.000 10.000 15.000 20.000
Instance Type db.t4g.medium db.t4g.medium db.t4g.large db.t4g.large db.t4g.large db.t4g.xlarge db.t4g.xlarge db.m6g.xlarge db.m6gx4xlarge
CPU 2 2 2 2 2 4 4 4 4
RAM 4 GB 4 GB 8 GB 8 GB 8 GB 16 GB 16 GB 16 GB 16 GB
Storage 50 GB 50 GB 50 GB 50 GB 50 GB 100 GB 100 GB 100 GB 100 GB

From these tables you can see that for a multi-node data center system with 2,000 users you should plan for approximately 16 GB RAM.

For a 2,000-user confluence system, this means approx. => 8-10 GB heap space. The Java code cache should be at least 512 or 768 MByte.

Please note, however, that these are only average orientation values!

In practice, an optimized heap results from the monitoring data and its analysis, in particular the heap usage, garbage collection and “time spent on garbage collection”.

Furthermore, the I/O speed and latency of the hard disk accesses should also be taken into account (especially with regard to the Confluence search index), as well as the “slow query logs” of the database system.

The technical articles from Atlassian are a particularly good guide here:

For detailed questions about optimizing the Confluence operating environment, Atlassian offers support:

“Contact an Atlassian Technical Account Manager for more guidance on choosing the right configuration for your Data Center instance. Our Premier Support team performs health checks by meticulously analyzing your application and logs to ensure that your infrastructure configuration is suitable for your Data Center application. If the health check process reveals any performance gaps, Premier Support will recommend possible changes.”

Single-Node Data Center

Productive system

License size (User) 10 25 50 100 250 500 1.000 2.000
vCPU 2 2 2 3 3 4 4 6
RAM 8 GB 8 GB 10 GB 10 GB 12 GB 16 GB 20 GB 20 GB
SSD 100 GB 100 GB 100 GB 100 GB 100 GB 150 GB 200 GB 240 GB