Office applications may be single-threaded, but if you need to open Word, Excel, and Powerpoint simultaneously they can each use a separate core. Similarly, you may need to run a web application at the same time as one or more Office applications. This sort of multiprocess parallelism still benefits from multiple cores.
As for "Windows ... is still single threaded", I'm not sure what you are talking about. The concept of a thread is part of the OS implementation.
If you need to run multiple applications simultaneously and they do sufficient amount of computations to generate noticeable load.
> Office applications may be single-threaded, but if you need to open Word, Excel, and Powerpoint simultaneously they can each use a separate core.
And idle. Unless you're actively editing a document, the applications are doing exactly nothing with their separate cores. And so far, our attempts to create four-armed employees able to write two concepts at the same time have hit some unexpected difficulties, so generally only one document is doing any CPU intensive work (and promptly hits 100% load for the single core it can use).
Excel would be an exception, if we did any heavy processing in it – which we don't. We have real databases for that. (And Postgres does scale nicely on its Xeon servers.)
> As for "Windows ... is still single threaded", I'm not sure what you are talking about.
Windows Defender / Security Essentials is singlethreaded, throttling all I/O to 50 MB/s effectively on an i5-6200U (and inducing crippling latency). Windows Explorer is singlethreaded (or has very unfortunate locking), so a single stalling I/O request (spinning up disk/CD drive; SMB over WAN) hangs up the device's entire UI. Windows Update is singlethreaded, resulting in hour-long churn while computing applicable updates. And so on. While you get some noticeable improvements from using a dual core, and a few more from using a dual core with hyperthreading, a full quad-core (with or without HT) is just a waste of silicon for our Windows clients.
On a typical desktop workload, at least the ones users at work put on their machines (i.e. running Windows, Office, a browser, maybe a PDF viewer and sometimes something like AutoCAD for P&ID) it is rare to fully utilize more than one or two CPU cores.
In fact, for performance on a typical office PC, the CPU hardly matters any more compared to I/O and (to some degree) RAM (and insufficient RAM again becomes I/O load when the swap-fest starts). When one of our users complains about performance, unless the machine still has a Core2, rather than replacing the CPU, we tend to upgrade RAM and/or replace the hard drive with an SSD.
And multithreaded JavaScript for webapps seems like a pipedream. Virtually no one uses Web Workers because they were designed to avoid sharing data between threads, making them inordinately cumbersome to use in any routine/real-world cases.
There is a lot of room for improvement across many fronts. But I am hopeful it will occur sooner or later because I suspect adding more cores will be easier than increasing the speed or each core for the foreseeable future.
For right now any settings other than one are not tested or supported. After electrolysis ships tuning the dom.ipc.processCount value based on the number of cores and and such is planned.
I don't know. Low-end i3s have 4 virtual cores, i5s 4 physical cores – and most consumer software still makes little use of even two. I just downgraded a bunch of users from quadcore 55W i7-HQ to dualcore 15W i5-U CPUs (laptops) – they don't notice a performance difference, because Windows and Office and all the web app bullshit is still single threaded.