Our current restore roachtest suite should be updated to better reflect customer workloads/topologies. I propose creating a default topology/workload and refactoring our existing tests to be more intentional in how they branch from the default configuration. Ideally, each test that deviates from the default configuration should explicitly test how this deviation affects performance. The new default configuration is described in detail here.

This issue will track work to:

• create a new roachtest with the default configuration
• modify restore2TB/nodes=10 to use the new default workload
• modify restore2TB/nodes=32 to use the new default workload
• modify restore2TB/nodes=6/cpus=16/pd-volume=2500GB to use the default workload, 4 nodes, and the default pd-ssd size

Epic CRDB-20915

Jira issue: CRDB-21924

Epic CRDB-20915