Cache hierarchies also exist because memory latency and capacity tend to be inversely proportional to each other, and directly proportional to cost. The underlying process and physics of chip design works against you on this front.
I'd love to have 1 GB of L1 cache, but that is simply not viable because your cache would be as big as your core, way more expensive, and by the sheer size, it would become a NUMA cache, which defeats the point of a cache and the "illusion" of UMA.
I think the greatest benefit of rethinking CPU architecture at the level of the ISA will be to make performance more transparent to developers without the layers of black magic.
Citation needed. After 10 minutes of searching I can't find anything to support this statement.
Because parallelism is not that needed, there’s always contention starting from physical constraint. A user can only have one body, a printer can only output one piece of paper at a time,… There are natural areas for parallelism and it’s been already implemented. Memory as a bottleneck has not been a things for decades.
Breaking down things in terms of tasks is not hard. The hard part is discovering that those parts need to communicate. And sometimes they want access to same limited resources. We already have things like array programming that have a parallel view of computation. But no one is rushing to get things done with them.
In a way I see the various cloud computing services as the organically grown (i.e. haphazard and clunky) answer to this problem.
But even that feels lacking, even though I'm really impressed with Seastar. I love the "bring operations to data" thinking.