Just because the Mac Studio has 20 cpu cores doesn’t suddenly mean the laws of programming are going to suddenly change.
Parallellizing most single threaded operations simply isn’t possible, or at best can only be split upon 4 cpu cores if you’re lucky.
Intel has been making mega multi-core cpus (Xeons) for a long long time and most apps can’t utilize all their cores.
The state of software isn’t going to change because of the Mac Studio.
This is indeed my opinion, if the rules of computing do not change with the accumulation of cores, then the most suitable target for a large number of cores is always "every second counts", and that's only if the software can use those cores effectively.
In my early years of working in multimedia and 3D, software had the benefit of multiple cores, but not all. Most of the time, the performance of a single core still dominates many workflows. Back then I used to work with C4D, AE, SKP, and the usual adobe software.
But there is no denying that good multi-core and good operating systems can be a significant benefit to multitasking.
However, more importantly, when choosing a powerful multi-core machine, users also need to know whether the software in use will be beneficial.
There is a very basic example, adobe PS in some cases or some scripts actually can not take full advantage of multi-core. This is because many processes are "One by One" and you have to wait for the last operation to finish before you can continue with the next one. This kind of project will not be able to enjoy the benefits of multi-core. But many people don't know that they think that by using efficient multi-core, they will get a lot of benefits from their work in PS, which is not the case. If a good user experience is achieved, it is probably due to the excellent duplexing of the operating system and the impact of the high-performance single core.
So as far as the Ultra is concerned, in terms of single-core performance, it's arguably the same as the average M1, with the significant benefit of more memory options and then greater performance freedom in the future if it gets either a software update or an update from Apple.
However, for those who don't work "every second counts", in terms of single-core efficiency, if we look at it from the point of view of "relying on a reasonable distribution of the operating system in multiple tasks, and the fact that most of the time we are actually working with single-core performance", I think the choice of metric is still single-core performance as the priority.
If the single core is strong enough, the multi-core will not be bad, but not every job can get the benefits of multi-core, as a professional user should have the ability to judge for themselves.
I never favored single-core performance until I started to realize that I was still affected by single-core performance in my life and at work, and that I could only get the benefits of multi-core in certain situations. If I always use "every second counts" as a reason to care about high performance multi-core machines, then the first thing I have to review is how much time I spend watching Youtube, FB, IG, Twitter or on "Like OR Dislike" things, and obviously how many times these things make me lose "every second counts", haha.