2,349 karma · joined September 12, 2014
Occam's razor in a situation where a hype man promised step-function improvements for well over a decade is that this is not an honest assessment or an assessment not based on honest data.
The worst OSX gets is trying to get me to agree to iTunes ToS once a month without a way to turn it off.
We at MotherDuck at working very closely with the DuckDB folks to build a DuckDB-based cloud service. I'm talking to various folks in the industry about the details in 1:1. Feel free to reach out to tino at motherduck.com.
(co-founder and head of Produck at MotherDuck)
(PM at MotherDuck)
https://www.hopkinsmedicine.org/health/conditions-and-diseas...
If the goal is to reduce abortions, then the pro-life strategy is less effective than pro-choice.
- Stability. It OOMS, your CTO mentioned that last week.
- It is not correct. I believe your team is aware of cases in which your very own benchmarks revealed Clickhouse to be incorrect.
- Scale. The distributed plan is broken and I'm not sure Clickhouse even has shuffle.
- SQL. It is very non-standard.
- Knobs. Lots of knobs that are poorly documented. It's unclear which are mandatory. You have to restart for most.
Don't get me wrong, I love open source, and I love what Clickhouse has done. I am not a fan of overselling. There are problems with Clickhouse. Trying to sell it as a superset of the modern CDW is not doing users any favors.
> Data lakes are better for ML / AI workloads, cheaper, more flexible, and separate compute from storage. With a data warehouse, you need to share compute with other users. With data lakes you can attach an arbitrary number of computational clusters to the data.
- I am not sure it's any cheaper than BQ or Snowflake storage.
- Modern CDW separates compute from storage.
- I am not sure what you mean by "you need to share compute with others". Why?
- You can attach an arbitrary number of "clusters" in BQ and Snowflake as well.
Additionally, modern CDW provides a very high level of abstraction and a very high level of manageability. Their time travel and compaction actually work, and their storage systems are continuously optimized for optimal performance.
I understand why folks want options. At the end of the day, folks want an easy to use, ALWAYS CORRECT stable database, with minimal well-documented predictable knobs, correct distributed execution plan, no OOMs, separation of storage and compute, and standard SQL, and Clickhouse struggles with all of the above.
(co-founder of MotherDuck)
(i was the pm for bigquery federation with gcs and cloudsql)
I did not catch you address correctness?
FWIW I have some experience with Clickhouse as I ran product at Firebolt and played a critical role in being more transparent about their foundations and giving credit where it is due. However, I do have some first hand experience with Clickhouse, which was jarring, considering my previous experience was with BigQuery.
(co-founder at MotherDuck)
Great post, and thanks for the call although i am skeptical of commodotization of OLAP systems thanks to the likes of substrait and velox. It'll take a lot of unwilling participants.
Here's one being quoted [0]
[0] https://www.carscoops.com/2022/12/tesla-investors-and-custom...