[BUG] `raft-ann-bench` fails to benchmark the build time of `faiss_cpu_flat`.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, python
- Domain
- performance, testing-qa
Research direction
Start by running the provided Docker reproduction for python -m raft-ann-bench.run with faiss_cpu_flat, then inspect the FAISS_CPU_FLAT_ANN_BENCH invocation and its output paths. Done means the benchmark no longer segfaults and creates datasets/glove-100-inner/result/build/faiss_cpu_flat,base.json alongside the saved index.
Written by the indexing model from the issue text.
Description
Describe the bug
raft-ann-bench fails to benchmark the build time of faiss_cpu_flat. The index seems to build successfully, as the index file is saved, but the result file is not created.
Steps/Code to reproduce bug
docker run --rm -u $(id -u) --gpus all --entrypoint /bin/bash --workdir /data/benchmarks -v .:/data/benchmarks rapidsai/raft-ann-bench:24.02a-cuda11.8-py3.10 -c 'eval "$(conda shell.bash hook)"
python -m raft-ann-bench.run --build --dataset glove-100-inner --algorithms faiss_cpu_flat --force'
Expected behavior
- An index file is built and saved as
./datasets/glove-100-inner/index/faiss_cpu_flat - Missing: A result file is produced
./datasets/glove-100-inner/result/build/faiss_cpu_flat,base.json
Additional context
Error message
Error occurred running benchmark: Command '['/opt/conda/bin/ann/FAISS_CPU_FLAT_ANN_BENCH', '--build', '--data_prefix=/data/benchmarks/datasets/', '--benchmark_out_format=json', '--benchmark_counters_tabular=true', '--benchmark_out=/data/benchmarks/datasets/glove-100-inner/result/build/faiss_cpu_flat,base.json.lock', '--raft_log_level=3', '--force', 'glove-100-inner_faiss_cpu_flat,base,k10,bs10000_a3f4f69a-c183-11ee-ad15-0242ac110003.json']' died with <Signals.SIGSEGV: 11>.
- Dominant language
- Cuda
- Stars
- 1k
- Forks
- 251
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
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.
More from NVIDIA/raft
-
doc
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 20/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
feature request
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Similar issues
-
area/sessions comp/agent P2 tool/skills type/perf
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NousResearch/hermes-agent#117788 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
open-goal/jak-project#4424 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100