Confluence 2.6 : Server Hardware Requirements Guide
This page last changed on Sep 17, 2007 by david.soul@atlassian.com.
Server administrators 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. Peak visitors are the maximum number of browsers simultaneously making requests to access or update the Confluence server. Visitors are counted from their first page request until the connection is closed and if public access is enabled, this includes internet visitors as well as logged in users. Minimum Hardware RequirementsOn small instances, server load is primarily driven by peak visitors. 5 Concurrent Users
25 Concurrent Users
Example Hardware SpecificationsThese 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.
Server Load & ScalabilityWhen 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.
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:
Maximum Reported UsagesThese values are largest customer instances reported to Atlassian or used for performance testing. Clustering for load balancing, database tuning and other performance tuning is recommended for instances exceeding these values.
Hard Disk RequirementsAll wiki content is stored in the database, while attachments use either the database or filesystem. For example, the wiki instance you are reading now uses approximately 13GB of database space. Private & Online ComparisonPrivate 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.
Related Pages
|
![]() |
Document generated by Confluence on Oct 10, 2007 18:48 |