Server Hardware Requirements Guide
Note: Please be aware that while some of our customers run Confluence on SPARC-based hardware, we only officially support Confluence running on x86 hardware and 64-bit derivatives of x86 hardware. Confluence typically will not perform well in a tightly constrained, shared environment - examples include an AWS micro.t1 instance. Please be careful to ensure that your choice of hosting platform is capable of supplying sustained processing and memory capacity for the server, particularly the processing-intense startup process.
Example hardware specifications
These are example hardware specifications for non-clustered Confluence instances. It is not recorded whether the amount of RAM refers to either the total server memory or memory allocated to the JVM, while blank settings indicate that the information was not provided.
3 machines total: application server, database server, Apache HTTPD + LDAP tunnel server.
Server load and scalability
When planning server hardware requirements for your Confluence deployment, you will need to estimate the server scalability based on peak visitors, the editor to viewer ratio and total content.
- The editor to viewer ratio is how many visitors are performing updates versus those only viewing content
- Total content is best estimated by a count of total spaces
Confluence scales best with a steady flow of visitors rather than defined peak visitor times, 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 512MB of memory
- Always use an external database, and check out the performance tuning guides.
Maximum reported usages
These values are largest customer instances reported to Atlassian or used for performance testing. Clustering, database tuning and other performance tuning is recommended for instances exceeding these values.
Most Internal Users
Most LDAP Users
Hard disk requirements
All page content is stored in the database, while attachments are stored in the file system. The more attachments you have, the more disk space you will require.
Private and public comparison
Private instances manage their users either internally or through a user repository such as LDAP, while online instances have public signup enabled and must handle the additional load of anonymous internet visitors. Please keep in mind that these are examples only, not recommendations:
For large instances, it may be worthwhile contacting an Atlassian Solution Partner for expertise on hardware sizing, testing and performance tuning.
Here's a breakdown of the disk usage and memory requirements of a large documentation site as at April 2013:
Home directory size
|Average memory in use||1.9 GB|
Size of selected database tables
Content and user properties
Content bodies (incl. all versions of blogs, pages and comments)
Content metadata (incl. title, author)
label (5982, 1264 kB),
content_label (134151, 46 MB)
Note: not all database tables or indexes are shown, and average row size may vary between instances.
Size of selected home directory components
Attachments (incl. all versions)
Did-you-mean search index
Office Connector cache
Usage index (now disabled)
Note: not all files are shown, and average file size may vary between instances.