RAG and vector searchLoading progress…

Dot product

Rank documents by dot product, cosine and L2 distance and explain the role of normalization and model choice.

Dot product as a score

The dot product q·d multiplies matching coordinates and adds them. It grows with how well d is aligned with q and with the length of d. Many retrieval models are trained to be used with a dot product, so the length can carry useful information. But if lengths vary for reasons that have nothing to do with relevance, they change the ranking.

length of document B10angle of document B (degrees)45length of document A (same direction as q)1
qAB
documentvectordot product with qrank
A[1, 0]12
B[7.07, 7.07]7.0711
dot product: grows with the length of the vector as well as its alignment with q larger is better

The defaults are the chapter's example: q = [1, 0], A = [1, 0], B = [10, 10] (length 14.1 at 45°). B ranks first although it points 45° away: its length wins.

The chapter's example: q = [1, 0], A = [1, 0], B = [10, 10].

Predict first. Does doubling a document vector double its dot product with a fixed query?

Chapter context

Semantic search represents queries and documents as vectors in a compatible space. Good retrieval depends on the encoder, its training objective and the candidate data; choosing a distance formula alone does not create semantic relevance.

Chapter reference: math, worked example & code

This section belongs to the whole chapter, so it is the same on every lesson in it and may cover a different lesson's topic. The code for the experiment you just ran is inside the experiment itself.

Math and notation

cos⁡(q,x)=qTx∥q∥∥x∥,∥q−x∥2=∥q∥2+∥x∥2−2qTx.\cos(q,x)=\frac{q^Tx}{\|q\|\|x\|},\quad \|q-x\|^2=\|q\|^2+\|x\|^2-2q^Tx.

For unit-normalized vectors, squared L2 is 2−2qTx2-2q^Tx, so their rankings agree under the appropriate direction. Zero vectors require a defined handling policy.

Worked example

Let q=[1,0], A=[1,0] and B=[10,10]. Raw dot products are 1 and 10, so B ranks first by dot product. Cosines are 1 and 1/sqrt(2), so A ranks first by cosine. This is a deliberate example of magnitude changing the retrieval objective.

Reference code

The following example uses the Python standard library and does not call a remote service.

from math import sqrt,isclose
q,a,b=[1,0],[1,0],[10,10]
dot=lambda u,v: sum(x*y for x,y in zip(u,v))
norm=lambda u: sqrt(dot(u,u))
assert dot(q,b) > dot(q,a)
assert dot(q,a)/(norm(q)*norm(a)) > dot(q,b)/(norm(q)*norm(b))
assert isclose(dot(q,b)/(norm(q)*norm(b)),1/sqrt(2))
assert 128*4 == 512

Python examples are provided for study and local execution; this page does not execute Python.

Common mistakes

Do not mix embedding spaces or metric directions. Normalize only when it matches the model and search objective. Similarity is not factual verification.