swaaye said:
If it was using unbuffered that could explain it I suppose.
We know, from the article, that the dual core Athlon 64 is running on a socket 939 board. Unless something else has changed I think it is very safe to assume the memory type is unregistered. We know for a fact that Opteron 250 is using registered RAM without the article stating this because this is always the case.
However, the dual-core chip is undoubtedly putting more stress on its single memory subsystem, whereas the dual Opterons have more overall bandwidth per chip than the dual core, per core.
I think you'll find that many 2P opteron boards use a shared memory controller where one CPU acts as master. I would also believe this to be the case in this benchmark, but I cannot prove that. Read on to find out why this is moot.
However, look at the Xeon (NetBurst) performance scaling and you can get a very strong hint that this test is not FSB dependent. NetBurst is very demanding on FSB/memory bandwidth. Now compare the single NetBurst 3.6GHz to the dual Xeon 3.6s that share an FSB. The 2P Xeon system scales very well. So well, in fact, that it suggests there is no FSB contention.
So this test doesn't seem like it would reveal the subtle nuances you may see going from a 2P Opteron system with independent memory busses to a shared bus dual core. However, for most intents and purposes the shared memory bus even on Opteron 2xx setups is not a major problem. The memory independence really only becomes important for very large scaling 4->8->beyond and certain applications. It would not make much sense to think and design in this direction for a desktop part meant to operate only as a 2P (dual core Athlons still cannot be coupled with more CPUs, you need an Opteron for that).
Is there any way this could really be better?.... The dual core A64 basically performs as well as dual Opterons, which I believe is the whole point of the dual core chip. K8 again demonstrates that AMD developed a very balanced, scalable chip. Now we get to look forward to dual dual-core chips, lol.
This was exactly the gist of my initial post. The Athlon 64 dual core is performing exactly as it should be expected without any real enhancement beyond the packaging and some benefits that may bring in terms of power consumption. So, it's great that dual core make the mainboard cheaper, in comparison to dual socket boards, and eveything simpler (chassis, PSU, etc, unregistered memory, etc), but it really has no "wow" beyond what is to be expected. That was my point.
My soon-to-be legendary missing post
P) addressed this aspect a bit more. By having two cores on one piece of silicon and in one package, you can do some magic that would be impossible with two separated cores such as in a 2P Opteron 250. AMD is not doing this (for now), but this would have been a real "wow! look at that!" as opposed to what we are seeing, which is completely predictable.