Re: Conroe has 4MB of cache compared to 1MB for K8.
K8 as 2M of cache when running multithreaded apps, which were included in the suite of benchmarks run on Conroe vs. K8.
Re: I have just given you a link which confirms from Fred Weber himself the lions share of the performance improvement
Yeah, and it was filled with ambiguities and a lack of data. He even uses 20% as his proof point number, so you should take it as an upper bound. He does not claim 20% is the average, but says it *can* be achievable on many "crucial" apps, which he does not define. It sounds more like an architect taking pride in his work, which is understandable. But it's certainly not *proof* that the IMC is the major contributer to K8 performance, as you claim.
Re: another big friggin clue for you, numerous benchmarks have shown that K7 and K8 perform virtually identically in cache bound work.
That would not entirely surprise me, depending on the benchmark. K8's improvements were in the SSE engine (which do not tend to be used in cache bound synthetic benchmarks), the front end (which would require more diverse traffic and instruction mix than one designed to be completely cache bound), and some aspects of the execution pipeline (which might not be affected by the type of computation used in the synthetic test in question). Why not name the benchmarks and speak to its strengths like an intelligent person, rather than closing your eyes and pointing randomly?
AI
Market Data 
Markets 
