From 41b3cdc0114ed79f7033a0b5711242a67b418e58 Mon Sep 17 00:00:00 2001 From: Andrew Kane Date: Sun, 26 Apr 2026 14:47:17 -0700 Subject: [PATCH] Updated readme [skip ci] --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 4efb949..4bc951e 100644 --- a/README.md +++ b/README.md @@ -746,13 +746,13 @@ VACUUM table_name; ## 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: 1. Use the `halfvec` type instead of `vector` for tables 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)). ## Monitoring