Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 6 additions & 7 deletions docs/reference/how-to/knn-search.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -72,14 +72,13 @@ least enough RAM to hold the vector data and index structures. To check the
size of the vector data, you can use the <<indices-disk-usage>> API.

Here are estimates for different element types and quantization levels:
+
--
`element_type: float`: `num_vectors * num_dimensions * 4`
`element_type: float` with `quantization: int8`: `num_vectors * (num_dimensions + 4)`
`element_type: float` with `quantization: int4`: `num_vectors * (num_dimensions/2 + 4)`
`element_type: float` with `quantization: bbq`: `num_vectors * (num_dimensions/8 + 12)`
`element_type: byte`: `num_vectors * num_dimensions`
`element_type: bit`: `num_vectors * (num_dimensions/8)`
- `element_type: float`: `num_vectors * num_dimensions * 4`
- `element_type: float` with `quantization: int8`: `num_vectors * (num_dimensions + 4)`
- `element_type: float` with `quantization: int4`: `num_vectors * (num_dimensions/2 + 4)`
- `element_type: float` with `quantization: bbq`: `num_vectors * (num_dimensions/8 + 12)`
- `element_type: byte`: `num_vectors * num_dimensions`
- `element_type: bit`: `num_vectors * (num_dimensions/8)`
--

If utilizing HNSW, the graph must also be in memory, to estimate the required bytes use `num_vectors * 4 * HNSW.m`. The
Expand Down
Loading