

On each update, dtSearch appends data to what is already in the index, without affecting fragmentation of the existing data. It might be more, because some updates might involve more than one commit (for example, if the update involves a lot of data).įragmentation is also affected by the amount of data that is fragmented. For example, if you build an index and then update it 5 times, fragmentation would be at least 6. Each time an index update commits, fragmentation of the index increases. In both cases, the data is not removed from the index but is tagged as "obsolete" for removal the next time the index is compressed.įragmentation occurs when an index is updated. Obsolete data comes from documents that are reindexed and from documents that are removed from the index.

Compressing an index optimizes the index structure, removing obsolete data and defragmenting search structures for better performance.
