topK
is less than 50, p2 pods support up to 200 QPS per replica and return queries in less than 10ms. This means that query throughput and latency are better than s1 and p1.
Each p2 pod has enough capacity for around 1M vectors of 768 dimensions. However, capacity may vary with dimensionality.
The data ingestion rate for p2 pods is significantly slower than for p1 pods; this rate decreases as the number of dimensions increases. For example, a p2 pod containing vectors with 128 dimensions can upsert up to 300 updates per second; a p2 pod containing vectors with 768 dimensions or more supports upsert of 50 updates per second. Because query latency and throughput for p2 pods vary from p1 pods, test p2 pod performance with your dataset.
The p2 pod type does not support sparse vector values.
x1
, x2
, x4
, and x8
. Your index storage and compute capacity doubles for each size step. The default pod size is x1
. You can increase the size of a pod after index creation.
To learn about changing the pod size of an index, see Configure an index.
environment
parameter for the create_index
endpoint:
Cloud | Region | Environment |
---|---|---|
GCP | us-west-1 (N. California) | us-west1-gcp |
GCP | us-central-1 (Iowa) | us-central1-gcp |
GCP | us-west-4 (Las Vegas) | us-west4-gcp |
GCP | us-east-4 (Virginia) | us-east4-gcp |
GCP | northamerica-northeast-1 | northamerica-northeast1-gcp |
GCP | asia-northeast-1 (Japan) | asia-northeast1-gcp |
GCP | asia-southeast-1 (Singapore) | asia-southeast1-gcp |
GCP | us-east-1 (South Carolina) | us-east1-gcp |
GCP | eu-west-1 (Belgium) | eu-west1-gcp |
GCP | eu-west-4 (Netherlands) | eu-west4-gcp |
AWS | us-east-1 (Virginia) | us-east-1-aws |
Azure | eastus (Virginia) | eastus-azure |