> You certainly know building and supporting that would cost more or less the same as building and operating a sizeable datacenter. If it succeeds.
There are plenty of solutions for that already. For the simplest case of the user-space networking, you can pick a number of "off the shelf" solutions for it:
http://lukego.github.io/blog/2013/01/04/kernel-bypass-networ... http://www.openonload.org/
You certainly know building and supporting that would cost more or less the same as building and operating a sizeable datacenter. If it succeeds.
Using all processing power a modern CPU offers on real code with real data is almost impossible. And it's not only memory latency and instruction interdependence - there are latencies all over a PC even before you leave the rackmount chassis. The supporting network is another source of uncontrollable latencies. Most apps I manage spend 99.99% of their time waiting for something to happen, be it the next packet, be the results from another server, which is actually a cluster behind one or more load balancers.
You may get some better cache hit ratios by tweaking thread/core affinity, but it won't take you to where you want to be.
If you really need that much performance, I'd suggest building your own VLIW architecture and generate the instruction mix on auxiliary CPUs as a single continuous thread on the fly based on all incoming requests for the VLIW core to devour. That would be a huge undertaking, but it would also be pretty cool CompSci.