What really happened was that cache misses kept increasing in latency (CPUs getting faster, memory isn't) and static scheduling simply cannot scale that far. M

What really happened was that cache misses kept increasing in latency (CPUs getting faster, memory isn't) and static scheduling simply cannot scale that far. Multiflow and friends would have exactly the same problem in a modern implementation - static scheduling is fundamentally hopeless. Transmeta did slightly better as CMS (the "JIT") could take advantage of biases discovered at runtime, but still couldn't do as well as a fully dynamic scheduler.