Originally Posted by EPiiKK
and that only if you benefit from HT in aplications stated above
Which outside some modern gaming engines and the actions of:
3DS/Maya/Rhino and whatever: RENDERING, not modeling in general, or even advanced simulations in particles and physics which are single threaded.
Photoshop/Lightroom (latest versions): EXPORTING images or JUST A FEW NOT THAT COMMON FILTERS, not general operations, cropping, rotating, resizing etc.
Premiere, AE and relative: again, only some preview effects and ofc exporting/transcoding is heavily threaded.
Windows: again those are multithreaded as in "running different stuff in different threads", not "oh, I split the work evenly and seamlessly to the idling cores/threads".
Not all operations can be threaded, and out of those that can, few can really be scaled to more than 1-2 extra threads before we get not only diminishing, but even negative effects.
Finally, for those operations that massive parallelism is actually beneficial, GPUs are picking up accelerating (at least Adobe and most rendering engine devs try to get deep into it).
So, whenever you hear someone talking about benefits in PS/AE/3DS and whatnot, take it with a grain of salt. The vast majority of stuff the average professional
does on this kind of apps, is not heavily threaded. If you doubt me, fire up your programs, go through your normal workday while logging CPU utilization. Now, the average hobbyist that does that once a week or less often, well...yeah...
Nothing is wrong with having a race car or even a GT-R in your garage...most of us would like to...
But the fact that you launched it hard a couple of times doesn't make you a race driver that out-grew anything less sophisticated or fast...it is just an expensive toy.
So are most enthusiasts' PCs. We like spending (wasting?) hours tweaking them, and then claim it was all justified for shaving those 2 secs off our real work task.
Yeah, well, I'm not impressed. But I justify it.
It is about the journey, not the destination.