Why are Go executable programs larger than expected? We visualized the CockroachDB binaries using tree maps to find out.
Disasters happen. (Most) outages shouldn't. So why do mission-critical services, like banking, still go dark in 2019?
This updated report includes the reproduction steps to our Cloud Report findings in which we benchmakred AWS and GCP. These steps allow for copy-paste reproduction of our process to empower you to check our work.
Customers rely on us to help navigate the complexities of the increasingly competitive cloud wars. This inspired the 2018 Cloud Computing Report, where we benchmark performance, latency, CPU, network, I/O, and cost of AWS and GCP.
CockroachDB 2.1 is 50x more scalable than Amazon Aurora at less than 2% of the price per tpmC. Read on to see performance benchmarks of CockroachDB 2.1, including the latest TPC-C results.
The decision to make CockroachDB and PostgreSQL compatible was driven by a desire to be accessible to an ecosystem of drivers, existing code, and developer knowledge.
We ran the TPC-C benchmark against CockroachDB and Amazon Aurora to compare price per transaction and discovered Aurora costs 10x more than CockroachDB.
CockroachDB achieves high OLTP performance of 128,000 tpmC on a 2 terabyte TPC-C dataset in size. This is 10x more TPC-C throughput than Aurora.
Learn which performance metrics matter, why to demand benchmark TPC-C results under serializable isolation, and how CockroachDB 2.0’s performance compares to 1.1.
In this post, we provide details on how CockroachDB uses system memory on each node, and what you can do to keep memory usage in CockroachDB under control.