Slow indexing

Indexing can be slow for a variety of reasons. Slow indexing can cause a backlog of index requests in the index request queue.

Monitoring operating system activity
For optimal performance, ensure that IBM® Content Search Services effectively uses your operating system resources. Use your operating system diagnostic tools and utilities to monitor system activity.
Troubleshooting queues
You can troubleshoot indexing performance by checking the status of the input and output queues.
Reviewing configuration and computer settings
Review these IBM Content Search Services and computer configuration settings that can impact IBM Content Search Services performance.
Text extraction indexing preprocessor considerations
When persistent text extraction (PTE) is enabled for a document class where Content Based Retrieval is already active, the standard CBR indexing pipeline is altered, resulting in reduced indexing performance.
IBM Content Collector considerations
IBM Content Search Services performs the text extraction step for any documents that are submitted to it by IBM Content Collector. A temporary directory stores the intermediate files that are created as a byproduct of indexing documents. In particular, the temporary directory is heavily used for text extraction. The intermediate files in the temporary directory might grow over time if you use IBM Content Collector.

Parent topic: Troubleshooting performance problems

Related concepts

Index request queue