Skip to content

Commit

Permalink
Update performance_faq.md
Browse files Browse the repository at this point in the history
  • Loading branch information
henryshere authored Sep 26, 2024
1 parent 58cc967 commit 085d2cb
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion site/en/faq/performance_faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ The following charts are results from a test running on the sift50m dataset and

#### Why do queries sometimes take longer on smaller datasets?

Query operations are conducted on segments. indexes reduce the amount of time it takes to query a segment. If a segment has not been indexed, Milvus resorts to brute-force search on the raw data—drastically increasing query time.
Query operations are conducted on segments. Indexes reduce the amount of time it takes to query a segment. If a segment has not been indexed, Milvus resorts to brute-force search on the raw data—drastically increasing query time.

Therefore, it usually takes longer to query on a small dataset (collection) because it has not built index. This is because the sizes of its segments have not reached the index-building threshold set by `rootCoord.minSegmentSizeToEnableindex`. Call `create_index()` to force Milvus to index segments that have reached the threshold but not yet been automatically indexed, significantly improving query performance.

Expand Down

0 comments on commit 085d2cb

Please sign in to comment.