Skip to content

Commit 2571bdb

Browse files
authored
Merge pull request #241 from vinnitu/patch-1
Update ALGO_PARAMS.md
2 parents 3c6a84f + 817e956 commit 2571bdb

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

ALGO_PARAMS.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,8 @@ elements for the queries. Note that in case the algorithm is not be able to find
1414
is 2-100. Higher ```M``` work better on datasets with high intrinsic dimensionality and/or high recall, while low ```M``` work
1515
better for datasets with low intrinsic dimensionality and/or low recalls. The parameter also determines the algorithm's memory
1616
consumption, which is roughly ```M * 8-10``` bytes per stored element.
17-
As an example for ```d```=4 random vectors optimal ```M``` for search is somewhere around 6, while for high dimensional datasets
18-
(word embeddings, good face descriptors), higher ```M``` are required (e.g. ```M```=48, 64) for optimal performance at high recall.
17+
As an example for ```dim```=4 random vectors optimal ```M``` for search is somewhere around 6, while for high dimensional datasets
18+
(word embeddings, good face descriptors), higher ```M``` are required (e.g. ```M```=48-64) for optimal performance at high recall.
1919
The range ```M```=12-48 is ok for the most of the use cases. When ```M``` is changed one has to update the other parameters.
2020
Nonetheless, ef and ef_construction parameters can be roughly estimated by assuming that ```M```*```ef_{construction}``` is
2121
a constant.

0 commit comments

Comments
 (0)