News for hackers. Stuff that matters.
Re:The death of CPU scaling: From one core to many — and why... by ChuckMcM on Thursday February 02, 2012 @07:02PM (#3545159)
I think we're basically in agreement, the parts where we differ are:

"- Certain e.g. graph constructs are difficult to partition. A single node compute engine that can scale up may turn out to be the more economically attractive option."

The unstated bias is what I might call 'conservation of compute' which is to say most of the work that has gone into partitioning such problems does so assuming that you want to find the answer in the fewest number of compute cycles because that will lead to the quickest result.

One of the things I got to witness at Google was the notion that you could relax the constraint on minimum number of cycles if those cycles could be run in parallel. This is done in a small scale in current micro-architectures where the processor speculatively continues computing past a branch on the 'bet' that the branch won't be taken, only to discard the results of that computation once it is known how the branch will go. This has shown to increase performance even if your branch prediction is only 50/50 because you avoid the pipeline stall when you're right.

My assertion is that the number of 'cores' and hence the number of compute engines you can apply to the problem, if you can decompose it into many speculative copies, will let you essentially compute many possible solutions in parallel and select the one you want through a 'fingerprint' of which branches would be or would not be taken. (the path through the graph as it were).

And this one:

"Not every company is Google/Facebook/Amazon -- with the attendant wealth of capital and human resources of these giants."

This is true, but both Google and Amazon have been making their infrastructure available on a pay per use basis. I expect this to continue. Then you will get domain specific portals into that infrastructure in which a middle layer of semantics sits between you and the infrastructure. Sort of like WolframAlpha putting Mathematica between you and WA's server farm, or S3 putting a storage layer between you and Amazons hardware.

I too root for some of these problems to be solved at the OS/hardware level but from the perspective of a companies willingness to put their data on another company's gear, at some point if you're being toasted by a competitor who has made that choice then the choice gets effectively made for you.

I'd love to write code on the bare metal of an upscale ARM chip with a graphics processor but as anyone who has tried to do this on an OMAP or Broadcom ARM chip can tell you, that isn't going to happen until you design your own ARM chip with GPU and build it yourself. I see this as an example of the choice I would like to make being denied me by forces outside of my control.

There are no comments on this comment yet.