Confluence 2.5 has reached end of life
Check out the [latest version] of the documentation
New users can use this guide in combination with the free Confluence trial period to evaluate their server hardware requirements. Because server load is difficult to predict, live testing is the best way to determine what hardware a Confluence instance will require in production.
Minimum Hardware Requirements
On small instances, server load is primarily driven by the peak number of anonymous or logged-in clients browsing or editing Confluence simultaneously.
5 Concurrent Users
- 1GHz+ CPU Pentium 4 or equivalent
- 256MB RAM
25 Concurrent Users
- Dual 2.4GHz CPU Pentium Xeon or equivalent
- 512MB+ RAM
Example Hardware Specifications
These are example hardware specifications for non-clustered Confluence instances. It not recorded whether the RAM refers to either total server memory or memory allocated to the JVM, while blank settings indicate that the information was not provided.
Accounts |
Spaces |
Pages |
CPUs |
CPU (GHz) |
RAM (Meg) |
|---|---|---|---|---|---|
150 |
30 |
1,000 |
1 |
2.6 |
1,024 |
350 |
100 |
15,000 |
2 |
2.8 |
700 |
5,000 |
500 |
|
4 |
3 |
2,024 |
10,000 |
350 |
16,000 |
2 |
3.8 |
2,024 |
10,000 |
60 |
3,500 |
2 |
3.6 |
512 |
21,000 |
950 |
|
2 |
3.6 |
4,048 |
Server Load & Scalability
When planning server hardware requirements for your Confluence deployment, you will need to estimate the server scalability based on peak concurrent users, the editor to viewer ratio and total content.
- Peak concurrent users is the maximum number of clients ever simultaneously browsing or editing Confluence, even if anonymous
- The editor to viewer ratio is how many clients are performing updates to versus those only viewing content
- Total content is best estimated by a count of total spaces
Confluence scales best with a low peak user load, few editors and few spaces. Users should also take into account:
- Total pages is not a major consideration for performance. For example, instances hosting 80K of pages can consume under 512 meg of memory
- Always use an external database
Maximum Reported Usages
The largest customer instances reported to Atlassian or created internally.
Most Spaces |
1700 |
Most Internal Users |
15K |
Most LDAP Users |
100K |
Most Pages |
80K |
