8 core 16 thread, 2.1 GHz base clock, 2.8 turbo, latest tick, latest tock, supports up to 128 gig ram so double the i7, mini itx boards @ 800 dollars including processor. No GPU though. Nice thing is, it does ECC ram. Oh and, 10Gbe. Awesome product. Not for gamers but superb for devs IMO. Throw in a gtx980 for display/compute, 1TB ssd, plus said 128 gig ecc ddr4 @ 1200 dollars, and you can do top-of-range mac pro class power for a third of the price. IE around 3.5k dollars before monitor for a very serious little rig. And if you're creative there are some stunning gamer cases for the mini itx form factor.
This is going to be "build your own" btw but anybody who's used a philips screwdriver can do this. Here in UK I have the total mentioned above at just over 2200 GBP including PSU and a cute Corsair case (http://is.gd/0pfKhg) so we're talking 3300ish dollars leaving 200 left for a pro mech KB and mouse. For the ram I had Crucial supply me for 780 british pounds (1200 USD ish) for 128 GB of 2400Mhz DDR4 ECC DIMMs (4 x 32 - there are only 4 slots so don't do 8 x 16), which works with these boards. As I said total including RAM about 2200 pounds so 3300 dollars. Or if you don't need 128GB start off with 64, say, but stick with the 32GB DIMMs so you can upgrade later.
http://www.newegg.com/Product/ProductList.aspx?Submit=ENE&DE...
Asrock Rack made some nice boards with onboard IPMI, dual Intel gigabit NICs, and 8x SATA. Kind of pricey but still under $500 for the board back in 2013. Been a great board: http://www.asrockrack.com/general/productdetail.asp?Model=C2...
Here's their Xeon D stuff: http://www.asrockrack.com/general/products.asp#Server
Denverton is the successor to Avoton; 16 cores, 16 lanes of PCI-E v3, 10GbE, DDR4: http://www.fudzilla.com/news/processors/39156-intel-s-denver...
Haven't heard anything about it for months, though.
I will have to consider this. I run a Mini-ITX board in a Micro-ATX case anyway. Perfect form factor.
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.
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 remember back in the day when SMP was the mark of a Real Programmer with a Real Computer. You kids today and your multicore processors! Fie!!
AMD tried exactly that with the Bulldozer architecture, which was a dismal failure. Desktop workloads are frequently bottlenecked on one or two cores.
36-core workstation based on Xeons: http://www.mediaworkstations.net/i-x2.html
Makes your MBP look pretty cheesy when you could have something like that under your desk. Then again, for developing rails and angular apps, you don't actually need it, and the PCI-E SSD makes a bigger difference in practice (you can RAID 0 NVME SSDs in workstations too though).
Server CPUs don't even use the same sockets they are fundamentally different.
Would software developers change their approach to coding if 32-core chips started to show up in consumer machines? I'd like to think so, but then again, I figured everything would be multithreaded by now.
(Which is sad because I want 16 core CPUs, but may be a long time because that isn't so useful for normal people)
You can turn hyperthreading on if possible
There's probably a narrow set of workloads that would benefit from more slower cores than 4 faster ones
The biggest bottleneck tends to be linking steps and other serialized items. (And those are getting better too; gcc's current linker supports parallelization using -j, integrated with make.)
I guess I kind of get why. Might be a socket compatibility and cost issue, the allocation of die space to a GPU, but it would nice to see some movement. Also probably zero demand outside of software developers, but I have to wonder if it is kind of chicken and egg problem.
It's actually kind of funny if I recall on desktops more of the die is GPU than CPU.