Why pay an extra $600 for a 2 TB internal SSD, after all fast external SSDs are cheaper. Maybe you need to check whether disk performance becomes a rate-limiting factor.
performance
The CPU view in Activity Monitor is the starting point for tuning the performance of software. Here are its virtues, and a few vices to beware of when using it.
Discovering whether using more threads makes a task faster gives insight into where its performance is limited. How to use a VM to investigate this.
What TB5 actually provides in its Symmetric and Asymmetric modes, why those are most important to connect Mac to dock or hub, and how that can go wrong.
Tuning your Mac for performance can be a good investment of time. Beware of general benchmarks, though, and develop your own objective measurements. Then identify the rate-limiting step methodically, so you can address that.
A first attempt to describe how macOS decides for a thread which type of core, which cluster, which core, what frequency, and how mobile it should be.
How macOS controls CPU P core cluster frequency according to the cluster total active residency, in synthetic in-core tests, compression and when running virtual machines.
A matrix multiplication test appears to be run on the AMX matrix co-processor, and behaves differently from in-core tests. And what Power modes really do.
Power use in two in-core performance tests, by number of threads run, leading to estimates of total energy used by P and E cores running the same code, at high frequencies. How efficient are the CPU cores in the M4?
In-core performance compared across P and E cores in M1, M3 and M4 chips shows substantial performance improvements, particularly in vector and matrix computation.
The Eclectic Light Company 