> The only performance that actually matters is single thread performance. I think users realized this and with manufacturing technology getting more expensive, companies are no longer keen on selling 16 core machines (of which the end user will likely never use more than 2-3 cores) just so they can win benchmark bragging rights.
How can you state something like this in all seriousness? One of the most used software application has to be the browser, and right now firefox runs 107 threads on my machine with 3 tabs open. gnome-shell runs 22 threads, and all I'm doing is reading HN. It's 2025 and multicore matters.
Those threads don't necessarily exist for performance reasons - there can be many reasons one starts a thread from processing UI events, to IO completion etc. I very much doubt Firefox has an easy time saturating your CPU with work outside of benchmarks.
If Firefox smears its CPU usage over multiple threads, that leaves more single-threaded performance on the table for other apps that may need it. So there could still be an effect on overall system performance.
Well yeah - what CPU bound task do you need to be performant? Beyond many tabs - which is embarrassingly parallel - it's all either GPU, network or memory bound.
Firefox failing to saturate your CPU is a win-state.
How can you state something like this in all seriousness? One of the most used software application has to be the browser, and right now firefox runs 107 threads on my machine with 3 tabs open. gnome-shell runs 22 threads, and all I'm doing is reading HN. It's 2025 and multicore matters.