Skip to content

Commit

Permalink
Update ALGO_PARAMS.md
Browse files Browse the repository at this point in the history
  • Loading branch information
vinnitu authored Aug 14, 2020
1 parent 3c6a84f commit 817e956
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions ALGO_PARAMS.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,8 +14,8 @@ elements for the queries. Note that in case the algorithm is not be able to find
is 2-100. Higher ```M``` work better on datasets with high intrinsic dimensionality and/or high recall, while low ```M``` work
better for datasets with low intrinsic dimensionality and/or low recalls. The parameter also determines the algorithm's memory
consumption, which is roughly ```M * 8-10``` bytes per stored element.
As an example for ```d```=4 random vectors optimal ```M``` for search is somewhere around 6, while for high dimensional datasets
(word embeddings, good face descriptors), higher ```M``` are required (e.g. ```M```=48, 64) for optimal performance at high recall.
As an example for ```dim```=4 random vectors optimal ```M``` for search is somewhere around 6, while for high dimensional datasets
(word embeddings, good face descriptors), higher ```M``` are required (e.g. ```M```=48-64) for optimal performance at high recall.
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.
Nonetheless, ef and ef_construction parameters can be roughly estimated by assuming that ```M```*```ef_{construction}``` is
a constant.
Expand Down

0 comments on commit 817e956

Please sign in to comment.