ClickHouse cost-efficiency in action: analyzing 500B rows on an Intel NUC

Re:ClickHouse cost-efficiency in action: analyzing 500B rows... by manigandham on Monday January 06, 2020 @05:21PM (#21974114)

It doesn't matter. ScyllaDB is a Cassandra clone, an advanced nested key/value database that stores data per-row and requires slow iteration to scan through an entire table.

Column-oriented databases will always be much faster at analytical queries because of the difference in physical layout and vectorized processing. Scylla's has very impressive OLTP performance but really shouldn't be compared to OLAP databases at all. That original 1B rows/sec blog post by them is kind of a strange benchmark to begin with.

[ Parent | on HN ]

Re:ClickHouse cost-efficiency in action: analyzing 500B rows... by astral303 on Tuesday January 07, 2020 @10:38AM (#21980933)

Problem is what use cases are strictly OLTP? At this point, I’d consider Scylla/C* to usable for a write-only workload with single-row lookups, or a single-column range lookup.

Same question has to be raised: do you have enough rows to justify a distributed Scylla/C* or could you have used MySQL or Postgres on a giant box?

[ Parent | on HN ]

Re:ClickHouse cost-efficiency in action: analyzing 500B rows... by manigandham on Tuesday January 07, 2020 @09:24PM (#21987676)

Plenty of OLTP scenarios that need distributed scale and/or high availability of C* - we use it for user profiles/session storage, counters and some high-volume logging that needs access to individual events.

[ Parent | on HN ]