Commit max batch size The max amount of documents (here jobs) per commit. To optimize indexing throughput, it is best to keep this as high as possible. However, especially when reindexing the whole instance, it can be useful to have a limit on how many jobs can be written without being committed. A commit will make the jobs available for search, constitute a "checkpoint" state in the indexing and will be logged. { if (v == null) { const { commit_job_max_batch_size: _, ...rest } = $values['indexer_settings'] $values['indexer_settings'] = rest } else { $values['indexer_settings'] = { ...$values['indexer_settings'], commit_job_max_batch_size: v } } }} />

Refresh index period (s) The index will query new jobs periodically and write them on the index. This setting sets that period. { if (v == null) { const { refresh_index_period: _, ...rest } = $values['indexer_settings'] $values['indexer_settings'] = rest } else { $values['indexer_settings'] = { ...$values['indexer_settings'], refresh_index_period: v } } }} />

Max indexed job log size (KB) Job logs are included when indexing, but to avoid the index size growing artificially, the logs will be truncated after a size has been reached. { if (v == null) { const { max_indexed_job_log_size: _, ...rest } = $values['indexer_settings'] $values['indexer_settings'] = rest } else { $values['indexer_settings'] = { ...$values['indexer_settings'], max_indexed_job_log_size: v * 1024 } } }} />