pgvector.git / summary / log / commit / refs
commit d158eefa6031e428caa497a6bb1c67e5df2ac748
Author: Andrew Kane <andrew@ankane.org>
Date: Sun Jun 11 00:47:41 2023 +0000
Updated guidance on probes [skip ci]
README.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.md b/README.md
index 1f823d28..e7ef8b0e 100644
--- a/README.md
+++ b/README.md
@@ -163,7 +163,7 @@ Three keys to achieving good recall are:
1. Create the index *after* the table has some data
2. Choose an appropriate number of lists - a good place to start is `rows / 1000` for up to 1M rows and `sqrt(rows)` for over 1M rows
-3. When querying, specify an appropriate number of [probes](#query-options) (higher is better for recall, lower is better for speed) - a good place to start is `lists / 10` for up to 1M rows and `sqrt(lists)` for over 1M rows
+3. When querying, specify an appropriate number of [probes](#query-options) (higher is better for recall, lower is better for speed) - a good place to start is `sqrt(lists)`
Add an index for each distance function you want to use.
[parent: a7bbb0772de9]