> Similarly for K8 wrt K7, the IMC was the right solution for
> many reasons (especially the scalability it gives to memory
> bandwidth in a multi-socket system), but for the broad range of
> workloads on the single socket client, I don't think you
> should expect more than 5-10% performance, with the rest
> coming from the many optimizations made to the K8 core.
I will most likely find out as I plan to buy a Conroe system
when they come out and can do some testing on some workloads
are considerably bigger than the caches.
But back to K7 vs K8: I've looked around to see what the
core improvements are and outside of the improvements in my
earlier post, all I've found to add to it are:
- pipeline's front-end instruction fetch and decode logic id refined to deliver a greater degree of instruction packing from the decoders to the execution pipe schedulers
- larger TLB for L1 and L2
and the second one is arguably memory related. Overall, the
list of non-memory related improvements from K7 to K8 looks
to me to be very small.