mirror of
https://github.com/pgvector/pgvector.git
synced 2026-06-06 05:51:21 +08:00
Updated readme [skip ci]
This commit is contained in:
@@ -746,13 +746,13 @@ VACUUM table_name;
|
|||||||
|
|
||||||
## Scaling
|
## Scaling
|
||||||
|
|
||||||
Scale vertically by increasing memory, CPU, and storage on a single instance. Use existing tools to [tune parameters](#tuning) and [monitor performance](#monitoring).
|
|
||||||
|
|
||||||
For a smaller working set:
|
For a smaller working set:
|
||||||
|
|
||||||
1. Use the `halfvec` type instead of `vector` for tables
|
1. Use the `halfvec` type instead of `vector` for tables
|
||||||
2. Use [binary quantization](#binary-quantization) for indexes (with re-ranking for search)
|
2. Use [binary quantization](#binary-quantization) for indexes (with re-ranking for search)
|
||||||
|
|
||||||
|
Scale vertically by increasing memory, CPU, and storage on a single instance. Use existing tools to [tune parameters](#tuning) and [monitor performance](#monitoring).
|
||||||
|
|
||||||
Scale horizontally with [replicas](https://www.postgresql.org/docs/current/hot-standby.html), or use [Citus](https://github.com/citusdata/citus) or another approach for sharding ([example](https://github.com/pgvector/pgvector-python/blob/master/examples/citus/example.py)).
|
Scale horizontally with [replicas](https://www.postgresql.org/docs/current/hot-standby.html), or use [Citus](https://github.com/citusdata/citus) or another approach for sharding ([example](https://github.com/pgvector/pgvector-python/blob/master/examples/citus/example.py)).
|
||||||
|
|
||||||
## Monitoring
|
## Monitoring
|
||||||
|
|||||||
Reference in New Issue
Block a user