Live data from Hacker News

CockroachDB 2.0 Performance Makes Significant Strides

cockroachlabs.com

11–20 of 187 posts

Re: CockroachDB 2.0 Performance Makes Significant Strides

#11
post #5

I'd love to hear from someone who has implemented this in production. Seems like really cool tech, but haven't had a chance to use it on a project yet.

Using it in production currently with dual-write and dual-read to compare perf. I'll do a write-up showing how Cockroach performs to Citus and Cassandra for my use case.

We use Citus and Memsql (big data analytics use cases). How does Cockroach handle joins and other OLAP style queries?

Re: CockroachDB 2.0 Performance Makes Significant Strides

#13
post #5

Earlier quoted context omitted.

Using it in production currently with dual-write and dual-read to compare perf. I'll do a write-up showing how Cockroach performs to Citus and Cassandra for my use case.

We use Citus and Memsql (big data analytics use cases). How does Cockroach handle joins and other OLAP style queries?

CockroachDB is not (yet) ready for use on OLAP-style workloads. Our performance work has focused on OLTP workloads so far. That said, we do great on OLTP joins (which is a stressed in the TPC-C workload).

Re: CockroachDB 2.0 Performance Makes Significant Strides

#15
post #5

Earlier quoted context omitted.

Using it in production currently with dual-write and dual-read to compare perf. I'll do a write-up showing how Cockroach performs to Citus and Cassandra for my use case.

We use Citus and Memsql (big data analytics use cases). How does Cockroach handle joins and other OLAP style queries?

You're not going to get better performance for OLAP than MemSQL's columnstore and in-memory rowstore for reference tables to join.

Citus is great if you want the Postgres interface but is still using standard rowstore tables. CockroachDB is similar with rowstore performance but with added distributed consensus overhead. They are both much better for OLTP and sharding. CockroachDB also provides easy high-availability and replication.

Re: CockroachDB 2.0 Performance Makes Significant Strides

#16
I will never use this product no matter how good it is due to its name. Hope you can understand that many ppl like me suffer phobia from cockroaches.

(PS: As expected ppl will downvote this, but just trying to give a very valuable feedback to ppl who don’t understand cockroach phobia.)

Re: CockroachDB 2.0 Performance Makes Significant Strides

#17
How much and what kind of memory and storage (SATA SSD, NVMe SSD, HDD?) is included in the 3 nodes used for testing? This benchmarking is really interesting but the next level is to understand the cost per tmpC measured. Memory especially and storage is a big component of cost these days.

Re: CockroachDB 2.0 Performance Makes Significant Strides

#18
post #5

Earlier quoted context omitted.

Using it in production currently with dual-write and dual-read to compare perf. I'll do a write-up showing how Cockroach performs to Citus and Cassandra for my use case.

We use Citus and Memsql (big data analytics use cases). How does Cockroach handle joins and other OLAP style queries?

We use clickhouse cluster with 1000 nodes and 50000 GB clickstream data.

Re: CockroachDB 2.0 Performance Makes Significant Strides

#19

Earlier quoted context omitted.

We use Citus and Memsql (big data analytics use cases). How does Cockroach handle joins and other OLAP style queries?

You're not going to get better performance for OLAP than MemSQL's columnstore and in-memory rowstore for reference tables to join. Citus is great if you want the Postgres interface but is still using standard rowstore tables. CockroachDB is similar with rowstore performance but with added distributed consensus overhead. They are both much better for OLTP and sharding. CockroachDB also provides easy high-availability…

Yeah this is what we do. Citus is our single source of truth and powers a few interactive apps and admin panels. These sync hourly to our Memsql cluster which is cstore + ref tables and works amazingly.

Re: CockroachDB 2.0 Performance Makes Significant Strides

#20

Earlier quoted context omitted.

We use Citus and Memsql (big data analytics use cases). How does Cockroach handle joins and other OLAP style queries?

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?
Post reply on HN