Thought this was Clickhole.com and was waiting for the payoff to the joke
ClickHouse gets lazier and faster: Introducing lazy materialization
101–110 of 130 posts
Re: ClickHouse gets lazier and faster: Introducing lazy materialization
#102We adopted ClickHouse ~4 years ago. We COULD have stayed on just Postgres. With a lot of bells, whistles, aggregation, denormalisation, aggressive retention limits and job queues etc. we could have gotten acceptable response times for our interactive dashboard. But we chose ClickHouse and now we just pump in data with little to no optimization.
We migrated some analytics workloads from postgres to clickhouse last year, it's crazy how fast it is. It feels like alien technology from the future in comparison.
Re: ClickHouse gets lazier and faster: Introducing lazy materialization
#103Earlier quoted context omitted.
I was under impression that servers and databases generally run on Linux though.
Windows still runs on 71% of the desktop and laptops [1]. In my experience a good number of applications start life on simple desktops and then graduate to servers if they are successful. I work in the field of analytics. I have a locked down Windows desktop and I have been able to try out all the other databases such as MySQL, MariaDB, PostgreSQL and DuckDB because they have windows installers or portable apps. I ha…
surely you have Docker though?
Re: ClickHouse gets lazier and faster: Introducing lazy materialization
#104is apache druid still a player in this space ? Never seem to hear about it anymore. why would someone choose it over clickhouse?
or Apache Doris ...I'm also curious
Re: ClickHouse gets lazier and faster: Introducing lazy materialization
#105We adopted ClickHouse ~4 years ago. We COULD have stayed on just Postgres. With a lot of bells, whistles, aggregation, denormalisation, aggressive retention limits and job queues etc. we could have gotten acceptable response times for our interactive dashboard. But we chose ClickHouse and now we just pump in data with little to no optimization.
We migrated some analytics workloads from postgres to clickhouse last year, it's crazy how fast it is. It feels like alien technology from the future in comparison.
are those like embedded analytics in the app or internal BI type workloads ?
Re: ClickHouse gets lazier and faster: Introducing lazy materialization
#106Earlier quoted context omitted.
chDB author here, You are right, we have not made a static libchDB. BTW, I guess you are a golang developer?
Correct! Would love to have the Go package come as a single dependency without having to distribute `.so` files. That's what's stopping me from using `chDB` now instead of DuckDB. Being able to use chDB in a static manner would also help deepen my usage of the Clickhouse server. Right now the Clickhouse side of my project is lagging behind the DuckDB one because of this.
That's great feedback, thank you! I just added your comment to the GH issue:
https://github.com/chdb-io/chdb/issues/101#issuecomment-2824...
Ps. I work for ClickHouse
Re: ClickHouse gets lazier and faster: Introducing lazy materialization
#107We adopted ClickHouse ~4 years ago. We COULD have stayed on just Postgres. With a lot of bells, whistles, aggregation, denormalisation, aggressive retention limits and job queues etc. we could have gotten acceptable response times for our interactive dashboard. But we chose ClickHouse and now we just pump in data with little to no optimization.
There's foreign data wrappers for Clickhouse that still allow Postgres as single point of consumption with all the benefits of Clickhouse deployment.
This is how we consume Langfuse traces!
Re: ClickHouse gets lazier and faster: Introducing lazy materialization
#108[dead]
Re: ClickHouse gets lazier and faster: Introducing lazy materialization
#109Late Materialization, 19 years later. https://dspace.mit.edu/bitstream/handle/1721.1/34929/MIT-CSA...
Same thing with columnar/vectorized execution. It has been known for a long time that's the "correct" way to process data for olap workflows, but only became "mainstream" in the last few years(mostly due to arrow).
It's awesome that clickhouse is adopting it now, but a shame that it's not standard on anything that does analytics processing.
Re: ClickHouse gets lazier and faster: Introducing lazy materialization
#110Earlier quoted context omitted.
We migrated some analytics workloads from postgres to clickhouse last year, it's crazy how fast it is. It feels like alien technology from the future in comparison.
are those like embedded analytics in the app or internal BI type workloads ?
For us these are just metrics on customer facing dashboards inside our app. They are basically realtime and show p95, p99, avg. etc over time ranges. Our app can show this for 1000s of entities in one dashboard and that can eat up resources pretty quickly