This guidance applies to pod-based indexes only. With serverless indexes, you don’t configure any compute or storage resources, and you don’t manually manage those resources to meet demand, save on cost, or ensure high availability. Instead, serverless indexes scale automatically based on usage.

If your index is at around 90% fullness, we recommend increasing its size. This can be done in two ways: either by changing the pod size being used or by adding additional pods.

​
Change Pod Size

You can easily increase the pod size from x1 up to x8 for your index’s pods, both within the console and using the API. Each x-factor increases the base pod’s capacity by that amount. So, an x4 pod is four times larger than an x1 pod. The price for the increased size is the same as adding that number of additional pods. So, a p1.x8 costs the same as eight p1.x1s.

​
Change via console

  1. Go to the console and log in.
  2. Switch to the Project that holds the index in question if it doesn’t load by default.
  3. Click the index you want to reconfigure.
  4. Click the … button.
  5. Select Configure.
  6. In the dropdown, choose the pod size to use.
  7. Click Confirm.

The size change will take up to 15 minutes to complete.

​
Change via API

Please take a look at configure_index() in our documentation for exact details on using the API to change your pod size.

​
Add Additional Pods

Adding additional pods to a running index is not supported. However, you can create a collection from an index and then create a new index from that collection.

For steps on creating the collection first, please take a look at backup indexes in our documentation.

For steps on creating an index from a collection, please take a look at Create an index from a collection in our documentation.

Was this page helpful?

Selecting index type and sizeUsing namespaces instead of several indexes