A recommendation system stores 3 million embeddings in Azure Database for PostgreSQL.
During peak hours, P95 similarity-query latency rises and the cache hit ratio drops significantly.
You suspect the vector-index working set no longer fits in memory, causing additional disk reads.
You must scale server resources and validate the result.
Which four actions should you take, in order?
Drag & Drop
Community Discussion