3 ms·

It's more like pay-for-what-you use. You can check out the pricing calculator for more detail: https://www.timescale.com/cloud-pricing https://www.timescale.com

It's more like pay-for-what-you use. You can check out the pricing calculator for more detail: https://www.timescale.com/cloud-pricing https://www.timescale.com/cloud-pricing Growing, shrinking, and migrating involve moving to a different instance type, so you have to select a different instance type. That being said, there is very very little downtime (on the order of 3-5 seconds while the DNS resolves)

akulkarni 7y ago
Plus growing, shrinking, migrating only requires a few clicks
solidasparagus 7y ago
Thanks for the clarifications, that's helpful. I wouldn't call it pay-for-what-you-use unless the pricing varies with your actual usage instead of changing when you change plans.
- dianasaur323 7y ago
  Interesting point of view - it's certainly always a bit hard to find the right verbage that everyone can understand, but hopefully this discussion clarified things!
  - dkersten 7y ago
    Last time I used a traditional hosting provider, I could get a new bare metal server setup in under half an hour. I would hardly call them "pay what you use" even though I could start and stop servers and change the plan I'm on and still be only two to three times slower than doing the same on AWS.
    - dianasaur323 7y ago
      Certainly - I've been seeing a bunch of usage based pricing that price on a different metric (like metrics per second) etc. Regardless, with Timescale Cloud, if you get a machine, you pay the price for that machine for as long as you use it. So I guess to avoid the confusion, we can call this just paying for the machine :)
      - dkersten 7y ago
        By the way, I've recently started using TimescaleDB (past month or two) for processing cryptocurrency trading information and I'm liking it a lot so far. I love that I can use Postgres as normal, but have efficient time-based queries. My first ever test query was to generate minutely OHLC+volume from time,price,quantity trades. It was pleasantly easy to do: select time_bucket('1 minutes', time) as minutely, max(price) as high, min(price) as low, first(price, time) as open, last(price, time) as close, sum(quantity) as volume from trades group by minutely order by minutely; https://gist.github.com/danielytics/e9b69933586e00732646e01657dde128 https://gist.github.com/danielytics/e9b69933586e00732646e016...
sansnomme 7y ago
How do you do live migrations? Do you shard, then suspend existing queries, and finally redirect?
- dianasaur323 7y ago
  We spin up a separate instance that matches the type that you want to migrate to, restore a backup and stream the WAL logs. Then, we redirect.
  - sansnomme 7y ago
    The good ol' event sourcing trick :D

akulkarni 7y ago

Plus growing, shrinking, migrating only requires a few clicks

solidasparagus 7y ago

Thanks for the clarifications, that's helpful. I wouldn't call it pay-for-what-you-use unless the pricing varies with your actual usage instead of changing when you change plans.

dianasaur323 7y ago
Interesting point of view - it's certainly always a bit hard to find the right verbage that everyone can understand, but hopefully this discussion clarified things!
- dkersten 7y ago
  Last time I used a traditional hosting provider, I could get a new bare metal server setup in under half an hour. I would hardly call them "pay what you use" even though I could start and stop servers and change the plan I'm on and still be only two to three times slower than doing the same on AWS.
  - dianasaur323 7y ago
    Certainly - I've been seeing a bunch of usage based pricing that price on a different metric (like metrics per second) etc. Regardless, with Timescale Cloud, if you get a machine, you pay the price for that machine for as long as you use it. So I guess to avoid the confusion, we can call this just paying for the machine :)
    - dkersten 7y ago
      By the way, I've recently started using TimescaleDB (past month or two) for processing cryptocurrency trading information and I'm liking it a lot so far. I love that I can use Postgres as normal, but have efficient time-based queries. My first ever test query was to generate minutely OHLC+volume from time,price,quantity trades. It was pleasantly easy to do: select time_bucket('1 minutes', time) as minutely, max(price) as high, min(price) as low, first(price, time) as open, last(price, time) as close, sum(quantity) as volume from trades group by minutely order by minutely; https://gist.github.com/danielytics/e9b69933586e00732646e01657dde128 https://gist.github.com/danielytics/e9b69933586e00732646e016...

sansnomme 7y ago

How do you do live migrations? Do you shard, then suspend existing queries, and finally redirect?

dianasaur323 7y ago
We spin up a separate instance that matches the type that you want to migrate to, restore a backup and stream the WAL logs. Then, we redirect.
- sansnomme 7y ago
  The good ol' event sourcing trick :D