Search Manual / Version 2010
Table Of ContentsThe Content Feeder sends content changes to the CoreMedia Search Engine in batches. You can configure the number of index documents in a batch and when to send a batch. Batch sizes and sending rate influence the indexing speed.
Note
Configuration not mandatory: Normally you do not need to change the default settings.
The Content Feeder sends a batch when one of the following conditions is fulfilled:
The maximum number of index documents in a batch has been reached.
The batch size in bytes would exceed the configured maximum if more index documents were added.
Maximum time delays are reached.
Use these properties to configure batch settings:
feeder.batch.max-size: The maximum number of index documents in a batch. A smaller batch may be sent if the maximum byte size is reached before.feeder.batch.max-bytes: The maximum number of bytes allowed in a batch. A smaller batch may be sent if the maximum batch size is reached before.feeder.batch.send-idle-delay: The maximum time in milliseconds to wait before sending a new batch if the Content Feeder is idle. This value should be small to update the index quickly and have up-to-date search results after some content was changed by an editor.feeder.batch.send-max-delay: The maximum time in milliseconds to wait sending a new batch if the batch is not yet full. This value normally is higher to avoid sending small batches, for example when large amounts of content are created by an import process.
Caution
Note, that open batches are kept in main memory. You have to reserve 2*maxBatchByteSize bytes for
the batches.