[citation][nom]alextheblue[/nom]I would never run anything artificially restricted to one thread, so in a purely real-world usage scenario, single-thread performance of software capable of running multiple threads is less-than-useful. However, as a complete nerd I still like to see the data. I just hate when those numbers get used and abused (not by you), when it doesn't even matter in many cases anymore.[/citation]
Well, in REAL world you are wrong and every programmer knows it. Most tasks are single-threaded dependant; even if program is multithreaded most internal tasks are single threaded. You can think of professional programs like Photoshop (some filters are not threaded well), CAD, Office, etc. So it's important that we have BOTH single thread performance and multithreading capabilities (just look at Handbrake performance). That's why that in a phone form factor a Cloverfield is generally better in applications than 8-core ARM.
Of course, this days any notebook CPU lower than 4 threads will be to slow, not because of multithreaded programs but because of multiple programs/applications in backgroud (multitabs browser, antivirus, etc).
Well, in REAL world you are wrong and every programmer knows it. Most tasks are single-threaded dependant; even if program is multithreaded most internal tasks are single threaded. You can think of professional programs like Photoshop (some filters are not threaded well), CAD, Office, etc. So it's important that we have BOTH single thread performance and multithreading capabilities (just look at Handbrake performance). That's why that in a phone form factor a Cloverfield is generally better in applications than 8-core ARM.
Of course, this days any notebook CPU lower than 4 threads will be to slow, not because of multithreaded programs but because of multiple programs/applications in backgroud (multitabs browser, antivirus, etc).