Timescale engineer here. Just want to point out that you can also attach additional disks using tablespaces, which are fully supported on hypertables. With a few simple commands, this allows you to add new disks and move old disks out of rotation while still being able to query the old data on them.
We prefer Google Cloud durable persistent storage. It may be started from a few GBs and then resized online up to 64TB per instance. This allows saving money by resizing disks only when needed. Such disks cost $40/TB/month. See https://cloud.google.com/compute/docs/disks/add-persistent-d...
Comments
The biggest problem I've had with timescale systems is managing the SSDs/HDDs underneath.
Having to resize/grow/stripe/etc. them is a pain.
So we came up with a clever solution that batches chunks to S3:
https://www.youtube.com/watch?v=x_WqBuEA7s8
$10/day for 100M records (100GB data), all costs!
And best yet, reduced DevOps! Very practical, super simple.
Timescale engineer here. Just want to point out that you can also attach additional disks using tablespaces, which are fully supported on hypertables. With a few simple commands, this allows you to add new disks and move old disks out of rotation while still being able to query the old data on them.
We prefer Google Cloud durable persistent storage. It may be started from a few GBs and then resized online up to 64TB per instance. This allows saving money by resizing disks only when needed. Such disks cost $40/TB/month. See https://cloud.google.com/compute/docs/disks/add-persistent-d...