Plan | Minimum usage |
---|---|
Standard | $50/month |
Enterprise | $500/month |
Usage below monthly minimum
Usage exceeds monthly minimum
Plan | Platform fee | Usage credits |
---|---|---|
Standard | $25/month | $15/month |
Enterprise | $500/month | $150/month |
Records | Dense dimension | Avg. metadata size | Avg. record size | Namespace size | RUs |
---|---|---|---|---|---|
500,000 | 768 | 500 bytes | 3.57 KB | 1.78 GB | 1.78 |
1,000,000 | 1536 | 1000 bytes | 7.14 KB | 7.14 GB | 7.14 |
5,000,000 | 1024 | 15,000 bytes | 19.10 KB | 95.5 GB | 95.5 |
10,000,000 | 1536 | 1000 bytes | 7.14 KB | 71.4 GB | 71.4 |
top_k
, include_metadata
, and include_values
, are not relevant for query cost; only the size of the namespace determines the number of RUs used.Fetched records | RUs |
---|---|
10 | 1 |
50 | 5 |
107 | 11 |
Records per batch | Dimension | Avg. metadata size | Avg. record size | WUs |
---|---|---|---|---|
1 | 768 | 100 bytes | 3.2 KB | 5 |
2 | 768 | 100 bytes | 3.2 KB | 7 |
10 | 1024 | 15,000 bytes | 19.10 KB | 191 |
100 | 768 | 500 bytes | 3.57 KB | 357 |
1000 | 1536 | 1000 bytes | 7.14 KB | 7140 |
New record size | Previous record size | WUs |
---|---|---|
6.24 KB | 6.50 KB | 13 |
19.10 KB | 15 KB | 25 |
3.57 KB | 5 KB | 9 |
7.14 KB | 10 KB | 18 |
3.17 KB | 3.17 KB | 7 |
Records per batch | Dimension | Avg. metadata size | Avg. record size | WUs |
---|---|---|---|---|
1 | 768 | 100 bytes | 3.2 KB | 5 |
2 | 768 | 100 bytes | 3.2 KB | 7 |
10 | 1024 | 15,000 bytes | 19.10 KB | 191 |
100 | 768 | 500 bytes | 3.57 KB | 357 |
1000 | 1536 | 1000 bytes | 7.14 KB | 7140 |
deleteAll
uses 5 WUs.
Records | Dense dimension | Avg. metadata size | Avg. record size | Namespace size |
---|---|---|---|---|
500,000 | 768 | 500 bytes | 3.57 KB | 1.78 GB |
1,000,000 | 1536 | 1000 bytes | 7.14 KB | 7.14 GB |
5,000,000 | 1024 | 15,000 bytes | 19.10 KB | 95.5 GB |
10,000,000 | 1536 | 1000 bytes | 7.14 KB | 71.4 GB |
Example
top_k
= 10p1.x2
pod with three replicas and a collection containing 1 GB of data. This project runs continuously for the month of January on the Standard plan. The components of the total cost for this example are given in Table 1 below:Table 1: Example billing componentsBilling component | Value |
---|---|
Number of pods | 1 |
Number of replicas | 3 |
Pod size | x2 |
Total pod count | 6 |
Minutes in January | 44,640 |
Pod-minutes (pods * minutes) | 267,840 |
Pod price per minute | $0.0012 |
Collection storage | 1 GB |
Collection storage minutes | 44,640 |
Price per storage minute | $0.00000056 |
Product | Quantity | Price per unit | Charge |
---|---|---|---|
Collections | 44,640 | $0.00000056 | $0.025 |
P2 Pods (AWS) | 0 | $0.00 | |
P2 Pods (GCP) | 0 | $0.00 | |
S1 Pods | 0 | $0.00 | |
P1 Pods | 267,840 | $0.0012 | $514.29 |
on_error="abort"
), you will still be charged for the records read. However, if the import fails because of an internal system error, you will not incur charges. In this case, the import will return the error message "We were unable to process your request. If the problem persists, please contact us at https://support.pinecone.io"
.
For the latest import pricing rates, see Pricing.