Skip to content

Latest commit

 

History

History
123 lines (87 loc) · 8.19 KB

regressions-dl20-passage-openai-ada2-int8.md

File metadata and controls

123 lines (87 loc) · 8.19 KB
Raw

Anserini Regressions: TREC 2020 Deep Learning Track (Passage)

NOTE: We're currently having issues with this regression, which throws "Retried waiting for GCLocker too often" errors.

Model: OpenAI-ada2 embeddings (using pre-encoded queries) with HNSW quantized indexes

This page describes regression experiments, integrated into Anserini's regression testing framework, using OpenAI-ada2 embeddings on the TREC 2020 Deep Learning Track passage ranking task, as described in the following paper:

Jimmy Lin, Ronak Pradeep, Tommaso Teofili, and Jasper Xian. Vector Search with OpenAI Embeddings: Lucene Is All You Need. arXiv:2308.14963, 2023.

In these experiments, we are using pre-encoded queries (i.e., cached results of query encoding).

Note that the NIST relevance judgments provide far more relevant passages per topic, unlike the "sparse" judgments provided by Microsoft (these are sometimes called "dense" judgments to emphasize this contrast). For additional instructions on working with MS MARCO passage collection, refer to this page.

The exact configurations for these regressions are stored in this YAML file. Note that this page is automatically generated from this template as part of Anserini's regression pipeline, so do not modify this page directly; modify the template instead and then run bin/build.sh to rebuild the documentation.

From one of our Waterloo servers (e.g., orca), the following command will perform the complete regression, end to end:

python src/main/python/run_regression.py --index --verify --search --regression dl20-passage-openai-ada2-int8

We make available a version of the MS MARCO Passage Corpus that has already been encoded with the OpenAI-ada2 embedding model.

From any machine, the following command will download the corpus and perform the complete regression, end to end:

python src/main/python/run_regression.py --download --index --verify --search --regression dl20-passage-openai-ada2-int8

The run_regression.py script automates the following steps, but if you want to perform each step manually, simply copy/paste from the commands below and you'll obtain the same regression results.

Corpus Download

Download the corpus and unpack into collections/:

wget https://rgw.cs.uwaterloo.ca/pyserini/data/msmarco-passage-openai-ada2.tar -P collections/
tar xvf collections/msmarco-passage-openai-ada2.tar -C collections/

To confirm, msmarco-passage-openai-ada2.tar is 109 GB and has MD5 checksum a4d843d522ff3a3af7edbee789a63402. With the corpus downloaded, the following command will perform the remaining steps below:

python src/main/python/run_regression.py --index --verify --search --regression dl20-passage-openai-ada2-int8 \
  --corpus-path collections/msmarco-passage-openai-ada2

Indexing

Sample indexing command, building HNSW indexes:

target/appassembler/bin/IndexHnswDenseVectors \
  -collection JsonDenseVectorCollection \
  -input /path/to/msmarco-passage-openai-ada2 \
  -generator HnswDenseVectorDocumentGenerator \
  -index indexes/lucene-hnsw.msmarco-passage-openai-ada2-int8/ \
  -threads 16 -M 16 -efC 100 -memoryBuffer 65536 -noMerge -quantize.int8 \
  >& logs/log.msmarco-passage-openai-ada2 &

The path /path/to/msmarco-passage-openai-ada2/ should point to the corpus downloaded above. Upon completion, we should have an index with 8,841,823 documents.

Note that here we are explicitly using Lucene's NoMergePolicy merge policy, which suppresses any merging of index segments. This is because merging index segments is a costly operation and not worthwhile given our query set. Furthermore, we are using Lucene's Automatic Byte Quantization feature, which increase the on-disk footprint of the indexes since we're storing both the int8 quantized vectors and the float32 vectors, but only the int8 quantized vectors need to be loaded into memory. See issue #2292 for some experiments reporting the performance impact.

Retrieval

Topics and qrels are stored here, which is linked to the Anserini repo as a submodule. The regression experiments here evaluate on the 54 topics for which NIST has provided judgments as part of the TREC 2020 Deep Learning Track. The original data can be found here.

After indexing has completed, you should be able to perform retrieval as follows:

target/appassembler/bin/SearchHnswDenseVectors \
  -index indexes/lucene-hnsw.msmarco-passage-openai-ada2-int8/ \
  -topics tools/topics-and-qrels/topics.dl20.openai-ada2.jsonl.gz \
  -topicReader JsonIntVector \
  -output runs/run.msmarco-passage-openai-ada2.openai-ada2.topics.dl20.openai-ada2.jsonl.txt \
  -generator VectorQueryGenerator -topicField vector -threads 16 -hits 1000 -efSearch 1000 &

Evaluation can be performed using trec_eval:

target/appassembler/bin/trec_eval -m map -c -l 2 tools/topics-and-qrels/qrels.dl20-passage.txt runs/run.msmarco-passage-openai-ada2.openai-ada2.topics.dl20.openai-ada2.jsonl.txt
target/appassembler/bin/trec_eval -m ndcg_cut.10 -c tools/topics-and-qrels/qrels.dl20-passage.txt runs/run.msmarco-passage-openai-ada2.openai-ada2.topics.dl20.openai-ada2.jsonl.txt
target/appassembler/bin/trec_eval -m recall.100 -c -l 2 tools/topics-and-qrels/qrels.dl20-passage.txt runs/run.msmarco-passage-openai-ada2.openai-ada2.topics.dl20.openai-ada2.jsonl.txt
target/appassembler/bin/trec_eval -m recall.1000 -c -l 2 tools/topics-and-qrels/qrels.dl20-passage.txt runs/run.msmarco-passage-openai-ada2.openai-ada2.topics.dl20.openai-ada2.jsonl.txt

Effectiveness

With the above commands, you should be able to reproduce the following results:

AP@1000 OpenAI-ada2
DL20 (Passage) 0.477
nDCG@10 OpenAI-ada2
DL20 (Passage) 0.676
R@100 OpenAI-ada2
DL20 (Passage) 0.723
R@1000 OpenAI-ada2
DL20 (Passage) 0.867

Note that due to the non-deterministic nature of HNSW indexing, results may differ slightly between each experimental run. Nevertheless, scores are generally within 0.005 of the reference values recorded in our YAML configuration file.

Also note that retrieval metrics are computed to depth 1000 hits per query (as opposed to 100 hits per query for document ranking). Also, for computing nDCG, remember that we keep qrels of all relevance grades, whereas for other metrics (e.g., AP), relevance grade 1 is considered not relevant (i.e., use the -l 2 option in trec_eval). The experimental results reported here are directly comparable to the results reported in the track overview paper.

Reproduction Log*

To add to this reproduction log, modify this template and run bin/build.sh to rebuild the documentation.