25 karma · joined May 15, 2021
It’s mainly focused on the insert batching which is why I was drawing attention to async_insert.
I think it’s worth highlighting the incremental transformation that CH can do via the materialised views too. That can often replace the need for a full blown streaming transformation pipelines too.
IMO, I think you can get a surprising distance with “just” a ClickHouse instance these days. I’d definitely be interested in articles that talk about where that threshold is no longer met!
If you need to ensure that you have super durable writes, you can consider, but I really think it’s not something you need to reach for at first glance
It’s recommended in the docs over the Buffer table, and is pretty much invisible to the end user.
At ClickHouse Inc itself, this scaled far beyond millions of rows per second: https://clickhouse.com/blog/building-a-logging-platform-with...
A way to “handle” partial substrings is to break up your input data into tokens (like substrings split in spaces or dashes) and then you can break up your search string up in the same way.
Easy to configure, easy to extend with Go, and slots in to alerting.
There’s differences in consumer rights effectively between a refund and compensation (like DR)
Easiest example is if you have a season ticket, but you have the day off. You weren’t going to take the train to work that day, so no intent to travel. If you claim DR, then that’s fraud for the compensation.
If you didn’t actually intend to travel, then claiming DR is fraud.
It will flag up quite quickly if you are “sniping” delayed trains at different times.
Just my feeling would be that I’d add the tenant ID before the timestamp as it should filter the parts more effectively
Now has an API (with some caveats)
Clear and concise articles that really dig into some of the hard technical problems with working at scale.
Has honestly made me a much better systems programmer since starting to read them.
It's certainly easier to figure out what's going on in a smaller container though! I've had to debug some nasty situation with layers in Python Lambdas before and it's not fun...
But NodeJS is second!
The underlying cause was that `ext4` filesystem was journalled and the `fsync`s were waiting on `jbd2_log_wait_commit`, which offcpu sampling let me pick up.
I don't think I would have been able to trace the kernel call and link it all the way back to the application call without BPF (at least I wouldn't have been able to).