Earlier quoted context omitted.
Yeah, though from what I understand this benchmark is measuring both transactional read and write performance rather than just join performance. Transactional writes are likely the slowest thing since they need to talk to all replicas.
Actually hmm, do reads need to talk to all replicas in this case (serializable isolation)?
CockroachDB 2.0 Performance Makes Significant Strides
141–150 of 187 posts
Re: CockroachDB 2.0 Performance Makes Significant Strides
#142Earlier quoted context omitted.
I think people are generally allowed to judge themselves without industry credentials...
That was tongue-in-cheek (that still had no business on HN), a reference to @lacker's two Putnam awards.
Re: CockroachDB 2.0 Performance Makes Significant Strides
#143The thing I really don't get is why CockroachDB is avoid benchmarking with it's rival tidb ( https://github.com/cockroachdb/docs/issues/1412 ). tidb already pretty mature, used in many big companies (Let's say, Didi, which on the similar scale data with Uber, and banks). Even if I like CockroachDB's pg sql more, it would be helpful to have the comparison/benchmark to show something more.
TiDB looks promising, but it doesn't have serializable transactions at all, which makes it something of an apples-to-oranges comparison at the moment when it comes to OLTP. TiDB has a weird kind of variation on "read committed" where you get phantom reads (though they're not called that in the documentation, which is actually ambiguous on this point). This is a problem for apps that expect consistency.
Re: CockroachDB 2.0 Performance Makes Significant Strides
#144Project idea: globally hosted / managed CockroachDB that lets developers quickly start building small apps cheaply or free using this database. This database has the potential to dethrone Spanner in a major way.
That’s on their roadmap: https://www.cockroachlabs.com/docs/stable/frequently-asked-q...
Re: CockroachDB 2.0 Performance Makes Significant Strides
#145Earlier quoted context omitted.
What kind of workload are you using it for? What's been your biggest win while using it?
A couple of our use-cases include: good KV access (stored user data etc.) and listing blocks of data that has been pre-sorted on disk at insert time (leaderboard records, chat message history etc.). As well, the clustering technology is particularly useful at scale. We work in the games space with some very large games in production, which allows us to spread the load across multiple database nodes and offers us peac…
Re: CockroachDB 2.0 Performance Makes Significant Strides
#146Earlier quoted context omitted.
We use clickhouse cluster with 1000 nodes and 50000 GB clickstream data.
That's only 50gb per node. Why do you/Clickhouse need so many nodes?
Re: CockroachDB 2.0 Performance Makes Significant Strides
#147Project idea: globally hosted / managed CockroachDB that lets developers quickly start building small apps cheaply or free using this database. This database has the potential to dethrone Spanner in a major way.
Re: CockroachDB 2.0 Performance Makes Significant Strides
#148Earlier quoted context omitted.
That’s on their roadmap: https://www.cockroachlabs.com/docs/stable/frequently-asked-q...
My Org/team is too conservative to use this is they have to hire ops and too froogle to use spanner.
Re: CockroachDB 2.0 Performance Makes Significant Strides
#149Re: CockroachDB 2.0 Performance Makes Significant Strides
#150The thing I really don't get is why CockroachDB is avoid benchmarking with it's rival tidb ( https://github.com/cockroachdb/docs/issues/1412 ). tidb already pretty mature, used in many big companies (Let's say, Didi, which on the similar scale data with Uber, and banks). Even if I like CockroachDB's pg sql more, it would be helpful to have the comparison/benchmark to show something more.
I'd really love some kind of distributed-for-performance database using the exact optimizer and query planner of SQLite plus std plugins (FTS5, JSON, transitive_closure, spatial). Something like a mix between Bloomberg's comdb2 (which uses a modified SQLite frontend) and rqlite (distributed-for-safety).
Note: You can save most of the shortcomings of CDB on the SQL client side today, but don't underestimate the time it takes to implement CDB-specific workarounds...