`max_optimization_threads: 0` doesn't disable indexing

[ffuugoo]

While running vector-db-benchmarks I've noticed that

• we are updating the collection with max_optimization_threads: 0 before uploading points
• and then once again with max_optimization_threads: 1 after upload is finished
• I assume this is done to disable optimization/indexing during points upload
• but I've noticed that max_optimization_threads: 0 doesn't disable indexing
  • I've disabled the max_optimization_threads: 1 request and had a collection fully indexed with max_optimization_threads: 0

If max_optimization_threads was intended to disable/enable indexing, then vector-db-benchmark can be updated to use indexing_threshold: 0 instead.

Screenshot

Notice indexed_vectors_count near the top and max_optimization_threads at the bottom.

[ffuugoo]

@generall Do we also want an issue in qdrant regarding max_optimization_threads: 0?

[KShivendu]

You're right about this @ffuugoo.

Will fix this in the next benchmarks run.