Confluence guardrails
Background
We’re committed to supporting the needs of our largest customers, and this includes continually improving the performance and scalability of our products. The amount of data in your instance can be a factor in performance and stability problems. As your instance grows, so does your risk of performance degradation over time. Often this is a gradual degradation and can go unnoticed until you reach a point where it has a significant impact on your team.
In the table below, we’ve described the performance and stability impacts that we’ve observed and suggested some actions you can take to reduce your risk. The guardrails are based on real-world experiences with some of our largest customers, but won’t necessarily be representative of every organization’s experience.
Ways you can reduce the risk of experiencing serious performance and stability problems may include:
application changes, such as upgrading to a newer application version to get the benefit of performance improvements, or changing the way users are managed.
infrastructure changes, such as increasing memory, CPU, or running a cluster or mirrors.
data cleanup activities to reduce your footprint, such as archiving or breaking up monolith sites.
It’s important to note that these aren’t hard limits, and some of your product instances may already exceed these thresholds. There are a number of factors, including the interplay between different data types, and site load, which will influence whether you experience the potential impacts listed below, and to what degree. As with any type of risk, it’s essential to identify the risk and make a plan, so you can prioritise those actions that will help you reduce the probability of future performance problems.
Definition
Product Guardrails are data type recommendations designed to help you identify potential risks and aid you making decisions about next steps in your instance optimization journey.
Confluence guardrails
The following guardrails are provided to help you identify and mitigate scale risks, and make decisions about cleaning-up your instance.
Index size
Content type | Total size of the index files in the home directory |
Guardrail | 30GB total file size, or 10,000,000 ‘Current versions’ items |
How to find this number | |
Risks | We've observed these problems when operating above this guardrail:
|
Mitigation options |
|
Spaces
Content type | Total number of spaces |
Guardrail | 10,000 spaces |
How to find this number | |
Risks | We've observed these problems when operating above this guardrail:
|
Mitigation options |
|
Space size (for import)
Content type | Total number of pages, blogs, attached files, version history, and trash in a single space |
Guardrail | Total size of 5GB for the entities.xml file within the space export zip file. |
How to find this number | |
Risks | We've observed these problems when operating above this guardrail:
|
Mitigation options |
|
LDAP users
Content type | Total number of users synchronised between LDAP and Confluence |
Guardrail | If using Microsoft Active Directory:
If using another connector:
|
How to find this number | How to get the number of users or groups |
Risks | We've observed these problems when operating above this guardrail:
|
Mitigation options |
|
LDAP groups
Content type | Total number of groups synchronised between LDAP and Confluence |
Guardrail | If using Microsoft Active Directory:
If using another connector:
|
How to find this number | How to get the number of users or groups |
Risks | We've observed these problems when operating above this guardrail:
|
Mitigation options |
|
Depth of nested groups
Content type | Number of levels of hierarchy when groups are nested |
Guardrail | 4 levels deep. We also recommend groups do not contain a mix of users and other groups, as this can also influence performance. |
How to find this number | You can’t get this number directly from Confluence. You’ll need to look at the hierarchies defined in your external directory. |
Risks | We've observed these problems when operating above this guardrail:
|
Mitigation options |
|