Live data from Hacker News

Ten years of ClickHouse in open source

clickhouse.com

61–70 of 110 posts

Re: Ten years of ClickHouse in open source

#61
post #38
post #11

I discovered ClickHouse around 2017-18 and built a PoC to replace Elasticsearch: 5x better storage and qps, in a couple of weeks. Managers rejected it because it wasn't well known and was seen as "some database made by Russians." On a personal level, it's quite sad to have seen that train coming so early and not been able to get on board.

Were you using it for simple grep search or actually required advanced searching for eg: BM25. Clickhouse will only help you with grep like search from what I understand.

Actually, there was no search, only on-the-fly aggregations/filtering over "big data". ES was kind of famous at the time, although not the best tool for that job.

afaik CH introduced FTS rececently.

Re: Ten years of ClickHouse in open source

#63
post #14

Earlier quoted context omitted.

How do you use it for visualization? Do you use ClickStack? or something else?

I have used SigNoz https://signoz.io/ for that

Worth noting both hyperdx and maple too for other observability on clickhouse options. https://www.hyperdx.io/ https://maple.dev/

Re: Ten years of ClickHouse in open source

#64
post #59
post #29

Earlier quoted context omitted.

Still via Grafana. I ran it side-by-side with Loki and despite trying to optimise Loki and using ClickHouse out of the box - it really was shocking how much faster ClickHouse was for every single query (e.g. in the last 12 hours give my the frequency of logs with a particular JSON event or even "find this log entry, then join back and find the number of times a different entry appears within the same correlation_id)

Interesting, so you can bind a Clickhouse table as an extension to Grafana? Would you make a little Gist / post about it to show?

You only need the plugin: https://clickhouse.com/docs/observability/grafana - then you get basically everything natively.

Re: Ten years of ClickHouse in open source

#65
post #62

It is sad they are afraid to mention on the page that "data processing for a web analytics system ... similar to Google Analytics" was actually something used in Yandex.

Elsewhere on the page, they avoid mentioning Yandex. In fact, do they ever mention Yandex?

That’s probably not to advertise for that company. I don’t see why it’s sad?

Re: Ten years of ClickHouse in open source

#66
We use Clickhouse in a rails app for our customer facing dashboard analytics, logging, and datalake type stuff where Postgres is too heavy and expensive. The web admin panel they built is great and we’ve had solid performance.

Re: Ten years of ClickHouse in open source

#67
For our metrics and autoscaling engine at Cloud 66, we went through 5 iterations before settling on Clickhouse: 1. Redis 2. Cassandra 3. Handrolled: Ruby + RabbitMQ 4. Handrolled: Go + RabbitMQ 5. Clickhouse

Every time we reached some limit or huge optimization burdens that were unfeasible. Clickhouse has been rock solid for the past 4 years.

Re: Ten years of ClickHouse in open source

#68

It's interesting that the blog post places SQLite and Ladybird on the spectrum, but omits it's chief open source rival: DuckDB. Agree that Level 3 is what inspires confidence. But we need to invent new business models to sustain in the era of vibe-coded databases.

while ClickHouse can scale down to compete with duckdb, I dont believe (but happy to be corrected) that duckdb can scale up like ClickHouse can.

most people dont have that scale problems, but when you do...

Re: Ten years of ClickHouse in open source

#69

Earlier quoted context omitted.

[flagged]

[flagged]

yes and the proof was the spam email phoning home to russia. or, whatever other hoaxes they cooked up along the way. strangely most of them didnt make it into the trial where he was acquitted.

Re: Ten years of ClickHouse in open source

#70
I used to keep all of OnlineOrNot's timeseries data entirely in a hot postgres db with the rest of the relational data.

Used to take a few seconds to get a week's uptime data and do some useful analysis.

Since moving to Clickhouse I think I can grab a full year's data in around 200ms (probably less if I try optimising it). Still completely blows my mind everyday.

Post reply on HN