SingleStoreDB as a Service with IBM
Deploy SingleStore DB as a Service with IBM with flexible pricing to give you control over your cost of operation. Resource Units are purchased to provide you with Compute, Storage, and Data Transfer usage.
Compute
Compute consumes a fixed number of Resource Units (credits) per hour, and can be scaled up or down to increase or decrease performance.
AWS
US West 2 (Oregon) - Tier 1
Standard
Size | vCPU | Memory | Credits per Hour (CR) |
|---|---|---|---|
S-00 | 2 | 16 GB | 0.25 CR |
S-0 | 4 | 32 GB | 0.5 CR |
S-1 | 8 | 64 GB | 1 CR |
S-2 | 16 | 128 GB | 2 CR |
S-4 | 32 | 256 GB | 4 CR |
S-6 | 48 | 384 GB | 6 CR |
S-8 | 64 | 512 GB | 8 CR |
S-12 | 96 | 768 GB | 12 CR |
S-16 | 128 | 1024 GB | 16 CR |
S-20 | 160 | 1280 GB | 20 CR |
Compute Resource Units
Compute Resource Units (credits) are used during the time in which SingleStoreDB with IBM deployments are running. Each deployment size and region corresponds to the rate at which Resource Units will be used. Overage usage is calculated monthly.
Editions
SingleStoreDB with IBM as a Service Compute Resource Units (credits) are tied to the edition of the product purchased. Resource Units purchased for SingleStoreDB with IBM 'Standard' are not applicable to 'Premium' and vice versa.
Regions
We recommend selecting a region close to where you will be transferring data to improve transfer times and data transfer fees. Each region is assigned to a Tier, which corresponds to the Compute, Storage, and Data Transfer credit consumption rates.
Sizes
These are sample deployment sizes, SingleStoreDB with IBM as a Service supports deployments much larger than shown above.
vCPU
A virtual CPU in SingleStoreDB with IBM as a Service corresponds to a single threaded processing core made available to run SingleStoreDB processes.
Memory
Memory is allocated in SingleStoreDB with IBM for running query workloads, storing row store tables which are persisted in memory, and caching columnstore tables persisted to disk.
Storage is tracked separately from Compute and Data Transfer usage. Each account comes with 3 TB of storage per month. Storage beyond 3 TB consumes Resource Units (credits) per 100 GB per Month. Storage charges are only incurred for storage used and are calculated based on the average total number of GB used per month. Object storage is allocated to SingleStore nodes and stores node-specific data as well as columnstore tables.
| Storage Tier | Tier 1 | Tier 2 | Tier 3 | Tier 4 |
|---|---|---|---|---|
| Credits per Avg 100 GB per Month | 1.5 CR | 1.75 CR | 1.75 CR | 2 CR |
Data Transfer is tracked separately from Compute and Storage. The first 10 TB of Ingress and 1 TB of Egress per month is included. Additional Data Transfer consumes Resource Units (credits) according to the Tier of the region.
| Data Transfer Tier Credits per 100 GB per Month | Tier 1 | Tier 2 | Tier 3 | Tier 4 |
|---|---|---|---|---|
| Transfer to same region, same cloud | 0 | 0 | 0 | 0 |
| Transfer to different region, same cloud | 1.5 CR | 1.5 CR | 7 CR | 7CR |
| Transfer to different cloud | 7 CR | 7 CR | 9 CR | 9 CR |