Managing index size in Confluence Data Center

This insight is shown when your Confluence Data Center's index size approaches or exceeds 10 million objects. Index size represents the total number of indexed content objects in your Confluence instance. This includes pages, blog posts, comments, and (if enabled) attachments. The value is captured in your support zip file under the <usage.content.current> tag.

How does large index size affect performance?

A large index can significantly impact your Confluence instance in several ways:

• Users experience noticeably slower search response times as the system takes longer to query and retrieve data.

• Administrative tasks like reindexing operations require extended completion times, consuming more system resources and potentially affecting overall system performance during these periods.

What's the recommendation?

You should aim to keep your index size below 10 million objects for optimal performance. If you're approaching or exceeding this threshold, consider the following actions:

Optimize attachment indexing

Attachment indexing can significantly contribute to your index size. You can disable content indexing for attachments while maintaining basic attachment search functionality:

1. Evaluate if you need full-text search for attachments

2. To disable attachment indexing:

   • Go to Confluence Administration > Configuration > Attachment Storage

   • Disable "Index attachments on creation"

Learn how to disable indexing attachments

Clean up unused spaces

Regular space maintenance can help manage index size:

1. Identify unused spaces:

   • Review space activity statistics

   • Look for spaces with no recent updates

   • Check for archived or obsolete projects

2. Before deletion:

   • Archive important but inactive spaces

   • Back up any necessary content

   • Communicate with space owners

Clean up your Confluence instance

Migrate to OpenSearch

OpenSearch provides better performance for large indexes:

• Faster reindexing times

• Improved search response times

• Better handling of large data volumes

Review OpenSearch hardware recommendations for Confluence

Optimize storage infrastructure

Storage performance directly impacts index operations:

1. Use SSD storage for:

   • Local home directory

   • Shared home directory

2. Ensure adequate I/O capacity

3. Monitor storage performance regularly

Preventive measures

To prevent index size issues in the future:

1. Implement regular space cleanup procedures

2. Monitor index size growth trends

3. Set up archiving policies for inactive content

4. Review attachment indexing requirements periodically