Problem Definition

On a busy Confluence instance, there could be thousands of content created or updated at a given time.
With automated content curation, the number of new items on the content index queue (or change queue) might be extremely large.

While the content index rebuild job is multi-threaded, the incremental indexing is performed by a single thread through a scheduled job.

Making the incremental indexing multi-threaded could improve Confluence usability making new content (created or updated) indexed as quickly as possible.

Suggested Solution

Make the incremental indexing multi-threaded having it configurable on how many threads will be used to take care of the task.
It could be similar to the reindex task on which the Confluence administrator can configure the number of threads through JVM parameters.