Performance Benchmarking with TPC-C

​

Before you begin

​

Review TPC-C concepts

​

Step 1. Set up the environment

• Provision VMs
• Configure your network

​

Provision VMs

1. Create 4 VM instances, 3 for CockroachDB nodes and 1 for the TPC-C workload.
   • Create all instances in the same region and the same security group.
   • Use the c5d.4xlarge machine type.
   • Use local SSD instance store volumes. Local SSDs are low latency disks attached to each VM, which maximizes performance. This configuration best resembles what a bare metal deployment would look like, with machines directly connected to one physical disk each. We do not recommend using network-attached block storage.
2. Note the internal IP address of each instance. You’ll need these addresses when starting the CockroachDB nodes.

​

Configure your network

• 26257 for inter-node communication (i.e., working as a cluster) and for the TPC-C workload to connect to nodes
• 8080 for exposing your DB Console

​

Inter-node and TPCC-to-node communication

​

DB Console

​

Step 2. Start CockroachDB

1. SSH to the first VM where you want to run a CockroachDB node.
2. .
3. Run the command:
   cockroach start \
   --insecure \
   --advertise-addr=<node1 internal address \
   --join=<node1 internal address,<node2 internal address,<node3 internal address \
   --cache=.25
   
4. Repeat steps 1 - 3 for the other 2 VMs for CockroachDB nodes. Each time, be sure to adjust the --advertise-addr flag.
5. On any of the VMs with the cockroach binary, run the one-time command to join the first nodes into a cluster:
   cockroach init --insecure --host=<address of any node on --join list
   

​

Step 3. Import the TPC-C dataset

1. SSH to the VM where you want to run TPC-C.
2. .
3. Import the TPC-C dataset:
   $ cockroach workload fixtures import tpcc \
   --warehouses=2500 \
   'postgres://root@<address of any CockroachDB node:26257?sslmode=disable'
   
   This will load 200 GB of data for 2500 “warehouses”. This can take a while to complete. You can monitor progress on the Jobs screen of the DB Console. Open the by pointing a browser to the address in the admin field in the standard output of any node on startup.

​

Step 4. Run the benchmark

1. Still on the same VM, create an addrs file containing connection strings to the 3 CockroachDB nodes:
   postgres://root@<node 1 internal address:26257?sslmode=disable postgres://root@<node 2 internal address:26257?sslmode=disable postgres://root@<node 3 internal address:26257?sslmode=disable
   
2. Run TPC-C for 30 minutes:
   $ cockroach workload run tpcc \
   --warehouses=2500 \
   --ramp=1m \
   --duration=30m \
   $(cat addrs)
   

​

Step 5. Interpret the results

_elapsed_______tpmC____efc__avg(ms)__p50(ms)__p90(ms)__p95(ms)__p99(ms)_pMax(ms)
 1800.0s    31064.6  96.6%    107.4     88.1    243.3    302.0    402.7    973.1

​

See also

• Hardware CockroachDB works well on commodity hardware in public cloud, private cloud, on-prem, and hybrid environments. For hardware recommendations, see our .
• Performance tuning For guidance on tuning a real workload’s performance, see , and for guidance on techniques to minimize network latency in multi-region or global clusters, see .