keep in mind TPC-C scales out in a trivial manner. It was designed before distributed databases existed. The workload itself is perfectly sharded on warehouse_id. All joins happen on this column and the query load is uniformly distributed on this key. This makes it perfect for distributed sql databases to scale out by sharding on warehouse_id (no hot spots and all joins and transactions will be local to one shard in the cluster)
This is one of the big reasons TPC-E was developed as a successor to TPC-C. It’s much harder to scale it out.
This is one of the big reasons TPC-E was developed as a successor to TPC-C. It’s much harder to scale it out.