---
title: BM25 Scoring
description: BM25 scores sort the result set by relevance
canonical: https://docs.paradedb.com/documentation/sorting/score
---

BM25 scores measure how relevant a score is for a given query. Higher scores indicate higher relevance.

## Basic Usage

The `pdb.score(<key_field>)` function produces a BM25 score and can be added to any query where any of the ParadeDB operators are present.

<CodeGroup>
```sql SQL
SELECT id, pdb.score(id)
FROM mock_items
WHERE description ||| 'shoes'
ORDER BY pdb.score(id) DESC
LIMIT 5;
```

```python Django
from paradedb import Match, ParadeDB, Score

MockItem.objects.filter(
    description=ParadeDB(Match('shoes', operator='OR'))
).annotate(
    score=Score()
).values('id', 'score').order_by('-score')[:5]
```

```ruby Rails
MockItem.search(:description)
        .matching_any("shoes")
        .with_score
        .select(:id)
        .order(search_score: :desc)
        .limit(5)
```

</CodeGroup>

In order for a field to be factored into the BM25 score, it must be present in the BM25 index. For instance,
consider this query:

<CodeGroup>
```sql SQL
SELECT id, pdb.score(id)
FROM mock_items
WHERE description ||| 'keyboard' OR rating < 2
ORDER BY pdb.score(id) DESC
LIMIT 5;
```

```python Django
from django.db.models import Q
from paradedb import Match, ParadeDB, Score

MockItem.objects.filter(
    Q(description=ParadeDB(Match('keyboard', operator='OR'))) | Q(rating__lt=2)
).annotate(
    score=Score()
).values('id', 'score').order_by('-score')[:5]
```

```ruby Rails
MockItem.search(:description)
        .matching_any("keyboard")
        .or(MockItem.where(rating: ...2))
        .with_score
        .select(:id)
        .order(search_score: :desc)
        .limit(5)
```

</CodeGroup>

While BM25 scores will be returned as long as `description` is indexed, including `rating` in the BM25 index definition will allow results matching
`rating < 2` to rank higher than those that do not match.

## Joined Scores

First, let's create a second table called `orders` that can be joined with `mock_items`:

```sql
CALL paradedb.create_bm25_test_table(
  schema_name => 'public',
  table_name => 'orders',
  table_type => 'Orders'
);

ALTER TABLE orders
ADD CONSTRAINT foreign_key_product_id
FOREIGN KEY (product_id)
REFERENCES mock_items(id);

CREATE INDEX orders_idx ON orders
USING bm25 (order_id, product_id, order_quantity, order_total, customer_name)
WITH (key_field = 'order_id');
```

Next, let's compute a "combined BM25 score" over a join across both tables.
The Django example assumes an `Order` model with `product = models.ForeignKey(MockItem, db_column='product_id', to_field='id', ...)`.

<CodeGroup>
```sql SQL
SELECT o.order_id, o.customer_name, m.description, pdb.score(o.order_id) + pdb.score(m.id) as score
FROM orders o
JOIN mock_items m ON o.product_id = m.id
WHERE o.customer_name ||| 'Johnson' AND m.description ||| 'running shoes'
ORDER BY score DESC, o.order_id
LIMIT 5;
```

```python Django
from django.db.models import F, FloatField
from django.db.models.expressions import RawSQL
from paradedb import Match, ParadeDB, Score

Order.objects.filter(
    customer_name=ParadeDB(Match('Johnson', operator='OR')),
    product__description=ParadeDB(Match('running shoes', operator='OR')),
).annotate(
    order_score=Score(),
    product_score=RawSQL('pdb.score(mock_items.id)', [], output_field=FloatField()),
).annotate(
    score=F('order_score') + F('product_score')
).values(
    'order_id', 'customer_name', 'product__description', 'score'
).order_by('-score', 'order_id')[:5]
```

```ruby Rails
orders = Order.arel_table
mock_items = MockItem.arel_table
combined_score = Arel::Nodes::Addition.new(
  orders[:order_id].pdb_score,
  mock_items[:id].pdb_score
)
join = orders.join(mock_items).on(orders[:product_id].eq(mock_items[:id])).join_sources

Order.joins(join)
     .search(:customer_name)
     .matching_any("Johnson")
     .search(mock_items[:description])
     .matching_any("running shoes")
     .select(
       orders[:order_id],
       orders[:customer_name],
       mock_items[:description].as("product_description"),
       combined_score.as("score")
     )
     .order(
       Arel::Nodes::Descending.new(combined_score),
       Arel::Nodes::Ascending.new(orders[:order_id])
     )
     .limit(5)
```

</CodeGroup>

## Score Refresh

The scores generated by the BM25 index may be influenced by dead rows that have not been cleaned up by the `VACUUM` process.

Running `VACUUM` on the underlying table will remove all dead rows from the index and ensures that only rows visible to the current
transaction are factored into the BM25 score.

```sql
VACUUM mock_items;
```

This can be automated with [autovacuum](/documentation/performance-tuning/overview).
