Skip to content

Commit 38f56f4

Browse files
committed
docs: explain about reranking
1 parent 4e1c676 commit 38f56f4

File tree

1 file changed

+14
-0
lines changed

1 file changed

+14
-0
lines changed

docs/guide/choosing-a-model.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -124,6 +124,20 @@ Here are a few concepts to be aware of when choosing a model:
124124

125125
Many embedding models include terms like `embed` in their name.
126126

127+
* **Reranking models** - models that are trained to rerank (sort) a list of documents
128+
based on their relevance to a given query.
129+
These models are usually smaller and faster than general-purpose models,
130+
making them more efficient and practical for reranking tasks.
131+
132+
Reranking models are often significantly smaller (sometimes as small as 500MB), faster,
133+
and consume less memory than general-purpose models, making them more efficient and practical.
134+
135+
While general-purpose models can also be used for reranking,
136+
doing this requires prompting the model, which is more cumbersome and inefficient than
137+
using a specialized model with a [ranking context](./embedding.md#reranking) for this task.
138+
139+
Many reranking models include terms like `rerank` or `reranker` in their name.
140+
127141
### How much data do you plan to feed the model at once with?
128142
If you plan to feed the model with a lot of data at once, you'll need a model that supports a large context size.
129143
The larger the context size is, the more data the model can process at once.

0 commit comments

Comments
 (0)