Cockroach Labs Estate economics What idle nodes, provisioned bytes and peak-sized bills cost, worked out from your estate.
  1. Nodes 9 baseline
  2. Avg CPU utilization 15.0% idle hardware
  3. Storage provisioned 150.0 TB 25.0 TB of data
  4. Est. monthly saving 0%

Step 4 of 8 - Storage

Scaling without copying the data

One action, both lanes. The only difference is where the bytes already are.

Fire an action Add a node Remove a node Scale to zero

Stateful nodes on EBS

8.3 TB to move

not started: 3 d 2 h to doStateful nodes on EBS progress8.3 TB to move. Not started: 3 d 2 h to do.

Data to move16667 ranges x 512 MB8.3 TB
Copy raterebalance snapshots are rate-limited per store32 MiB/s
Time to complete8.3 TB at 32 MiB/s, and the docs give a band of minutes to hours3 d 2 h
Consequencecan't shrink quickly, so provision for peakpeak-provisioned

Stateless KV nodes, disaggregated storage

1042 KB of metadata

not started: under a second to doStateless KV nodes, disaggregated storage progress1042 KB of metadata. Not started: under a second to do.

Hard links created16667 ranges shared, not copied16667 links
Metadata written16667 x 64 bytes1042 KB
Time to complete1042 KB at 32 MiB/sunder a second
Bulk data movednone: the range's SSTables are shared, not copied0 GB
Still sentthe range's store-local state, which no hard link sharessmall
How this is worked out
  • Both bars run in real time. A second on screen is a second of the actual operation: the hard links are written in under a second and the copy needs 3 d 2 h, so the left-hand bar is still going when you leave the page. There's nothing to wait for.
  • Moving a range is rate-limited per store, so the duration is arithmetic: 8.3 TB at 32 MiB/s, which is CockroachDB's default kv.snapshot_rebalance.max_rate. It's the optimistic end - a real rebalance shares the link with your queries - and it lands inside the "minutes to hours" the design docs give.