News for hackers. Stuff that matters.
Re:InfluxDB CTO: Why We Moved from Go to Rust by the_duke on Sunday October 01, 2023 @12:20PM (#37727475)
Fair warning, I had serious scaling issues with Timescale.

Solutions like Grafana Mimir, Victoria Metrics, Clickhouse, or yes, the new Influx implementation, are much more scalable and will give you much fewer headaches.

ClickhouseDB is realy brilliant, btw, it's a powerhouse. Especially with the fairly recent additions that enable hybrid local + S3 option, pushing older metrics to S3 for cheap long-term storage.

Re:InfluxDB CTO: Why We Moved from Go to Rust by PaulWaldman on Sunday October 01, 2023 @12:34PM (#37727662)
Can you elaborate on what scaling issues you had with Timescale?
Re:InfluxDB CTO: Why We Moved from Go to Rust by efxhoy on Sunday October 01, 2023 @12:40PM (#37727755)
I ran into issues with TS too. Main issue I recall now was maintaining a grand total count of events that were already rolled up into daily counts was not fast since it always looked back at all the data. There was no way in the ts patterns to efficiently express it without handrolling something. The issue was that a grand total count can’t be expressed in terms of a hypertable because there’s no time column.

It’s fantastic for workloads that neatly fit in the hypertable pattern though.

Re:InfluxDB CTO: Why We Moved from Go to Rust by lispisok on Sunday October 01, 2023 @03:46PM (#37729831)
You tried to use a timeseries database without a time column?
Re:InfluxDB CTO: Why We Moved from Go to Rust by efxhoy on Sunday October 01, 2023 @06:46PM (#37731737)
> Don't be snarky.

https://news.ycombinator.com/newsguidelines.html

Are you expecting a real answer of how I was hoping timescale's internal watermark system would help me roll up a total count or are you just implying I'm an idiot?

Re:InfluxDB CTO: Why We Moved from Go to Rust by mardifoufs on Sunday October 01, 2023 @07:03PM (#37731873)
What's the difference between the watermark and a time column? Not the person you were replying to but I'm curious since I also thought that TimeseriesDB had a similar "timestamp" to influx.
Re:InfluxDB CTO: Why We Moved from Go to Rust by efxhoy on Sunday October 01, 2023 @07:30PM (#37732065)
TS requires you to specify a time column in each hypertable or view (continuous aggregate) where you want it to work its magic. It then stores an internal watermark that it compares to the time column in the table to figure out from where to read when refreshing.

My issue was that for a grand total I didn’t have a time column, so I couldn’t define my query as a continuous aggregate and the query had to start counting from the start of my underlying series each time.

Re:InfluxDB CTO: Why We Moved from Go to Rust by pbronez on Monday October 02, 2023 @08:39AM (#37737309)
Perhaps: add a time column with an artificially huge time range? This defines the grand total as an interval sum that happens to include all possible intervals.
Re:InfluxDB CTO: Why We Moved from Go to Rust by mfreed on Sunday October 01, 2023 @01:03PM (#37728001)
If you are open, would love to hear more about some of the challenges you had with Timescale, esp. with your workload.

mike (at) timescale or DM on twitter?

Re:InfluxDB CTO: Why We Moved from Go to Rust by atombender on Sunday October 01, 2023 @02:03PM (#37728628)
The cloud storage option for CH looks like a game changer for time-based data. Any concerns there about accidentally causing "trashing" when cold data is needed? I believe the MergeTree system works by splitting the table into parts during insertion that then later get merged together, so you have to careful that during merging, only the "hot" data is touched, otherwise you'll start pulling in cloud storage data that's supposed to be effectively read-only.
Re:InfluxDB CTO: Why We Moved from Go to Rust by the_duke on Sunday October 01, 2023 @03:13PM (#37729452)
The merging happens primarily on hot data, I haven't run into any issues there.

But there are lots of approaches, depending on your needs.

You can (should) define a "cache disk" for S3, which will cache up to X Gb locally to avoid trashing.

Another option is is to move data into separate (purely S3 backed) tables after a certain time to avoid accidentally fetching large amounts of data from S3. You can still easily join the data together if needed.

Re:InfluxDB CTO: Why We Moved from Go to Rust by mxstbr on Sunday October 01, 2023 @02:08PM (#37728674)
Agreed. We initially used Timescale for our GraphQL Metrics product[0] but very quickly ran into scaling & performance issues. We switched to Clickhouse and have scaled 10.000x+ since with almost no issues.

[0]: https://stellate.co/graphql-metrics

Re:InfluxDB CTO: Why We Moved from Go to Rust by mfreed on Sunday October 01, 2023 @02:08PM (#37728678)
Also, Timescale similarly introduced S3 for bottomless data tiering:

https://www.timescale.com/blog/expanding-the-boundaries-of-p...

Re:InfluxDB CTO: Why We Moved from Go to Rust by wtfishackernews on Sunday October 01, 2023 @05:46PM (#37731195)
Only for their managed solution at the moment.