IBM Support

Key Parameters to Tune IBM Content Collector (ICC) for desired throughput

Technical Blog Post


Abstract

Key Parameters to Tune IBM Content Collector (ICC) for desired throughput

Body

ICC has two key parameters to control system throughput: Thread count and Queue size These parameters can both be set by using the ICC Configuration Manager by selecting Task Route Service Configuration in the Tools menu.

image

Thread count:

The Thread count parameter determines the maximum number of concurrently
processed items. As a rule of thumb, a number of two to four threads for each
physical CPU core should be configured for high throughput scenarios. Content
Collector ships with a default setting of 16 threads, which is adequate for most
deployment scenarios. If a high number of CPU cores are available, the number
of threads may be increased. If the throughput of the Content Collector server
should be throttled, the number can be decreased. A typical scenario for
throttling is to reserve CPU resources for the interactive search, view, and
restore workload or to prevent an overloading of the email or file server. You
should not configure a thread count of less than two threads.
Queue size:
The Queue size parameter defines the number of items that a collector can
submit. It acts as a buffer between the submitting connector and the processing
tasks. In practice, values between 64 items (file archiving) and 128 items
(high-throughput email archiving deployments) have been used with good
results. You can use a maximum value of up to 256 items for eight core servers
in Lotus Domino based systems and when scale-out setups are used.

Guidence has been provided on these parameters in the IBM Redpaper titled "IBM Content Collector Deployment and Performance Tuning".

[{"Business Unit":{"code":"BU029","label":"Data and AI"}, "Product":{"code":"SSAE9L","label":"Content Collector"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":""}]

UID

ibm11139020