The maxcheck parameter has no effect when searching.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 5k
- Forks
- 622
- Avg merge
- 8h 37m
- Merged PRs (30d)
- 5
Description
I ran the code following the example, but while searching I found that the MaxCheck parameter doesn't adjust the recall as described.
[1] [query] [maxcheck] [avg] [99%] [95%] [recall] [qps] [mem]
[1] 0-10000 16384 0.0028 0.0090 0.0064 0.8103 2886.7361 0GB
[1] 0-10000 8192 0.0024 0.0086 0.0056 0.8103 3368.8591 0GB
[1] 0-10000 4096 0.0015 0.0058 0.0033 0.8103 5320.0259 0GB
[1] 0-10000 2048 0.0015 0.0060 0.0035 0.8103 5267.8604 0GB
[1] 0-10000 1024 0.0016 0.0055 0.0036 0.8103 5104.4990 0GB
[1] 0-10000 512 0.0014 0.0050 0.0032 0.8103 5527.0239 0GB
[1] 0-10000 256 0.0016 0.0054 0.0037 0.8103 4964.4180 0GB
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported example using the listed MaxCheck values and compare recall, latency, and QPS. Trace the C++ search path to determine where maxcheck is handled; done means the parameter affects recall as described or the issue is documented with a confirmed explanation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100