Skip to content
This repository has been archived by the owner on Apr 4, 2023. It is now read-only.

Introduce a threshold to the asc/desc sorting criteria #49

Closed
Kerollmops opened this issue Dec 11, 2020 · 0 comments · Fixed by #127
Closed

Introduce a threshold to the asc/desc sorting criteria #49

Kerollmops opened this issue Dec 11, 2020 · 0 comments · Fixed by #127
Labels
good first issue Good for newcomers

Comments

@Kerollmops
Copy link
Member

The current Asc/Desc criteria choose between two ways of doing the job:

  1. If the number of candidates is lower or equal to 1000, it does a simple sort.
  2. If the number of candidates is bigger than 1000, it uses the facet database.

This number (1000) should better be a percentage of the total number of documents. It could be something like 0.1%. This way, we ensure that the best technique is used even if the database grows. #48 helps in retrieving the number of documents and, therefore, speedups computing a percentage.

@Kerollmops Kerollmops added the good first issue Good for newcomers label Dec 11, 2020
@Kerollmops Kerollmops changed the title Introduce a threashold to the asc/dec sorting criteria Introduce a threshold to the asc/dec sorting criteria Dec 14, 2020
@Kerollmops Kerollmops changed the title Introduce a threshold to the asc/dec sorting criteria Introduce a threshold to the asc/desc sorting criteria Dec 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant