4 ms·
This is already the second Postgres solution with bottomless storage in S3 as Neon provides that as well. For me, the neatest feature of Neon is that it can sca
by tuukkah 4y ago
This is already the second Postgres solution with bottomless storage in S3 as Neon provides that as well. For me, the neatest feature of Neon is that it can scale to zero whenever there are no requests (so truly cloud-native and serverless in that sense too), but I don't see a mention whether Timescale will have the same.
- sgichohi 4y agoTo my understanding, Neon stores all its data in pageservers and s3 (where together they are used as a write-back page cache, with S3 as the bottom-most layer). Timescale gives users a lot more control. S3 is used for storage of older data while newer data is stored on faster disks. The workload patterns for use cases like time-series, events, and analytics fit this well. The time dimension often gives a clear separation between what should be stored in hotter storage and what should be stored in cooler storage, based on time-oriented nature of data. We also leverage a compressed columnar format that makes our data space and scan efficient for time series workloads. Neon stores a database page friendly format that best supports their workloads. (Timescale engineer)
- nikita 4y agoThat's right. Our approach is "no knobs". We think the system can make better decision on what should be offloaded to S3 vs kept on the pageservers which leads to zero configuration to the users.
- yencabulator 4y ago> For me, the neatest feature of Neon is that it can scale to zero As far as I understood, Neon is only scale-to-zero from the perspective of a tenant ("don't bill for idle"), not from the perspective of who's running the software. Neon's compute nodes can scale down to zero, but the pageservers and safekeepers don't. And since safekeepers are a Paxos quorum, there's at least 3 of them!