Bulldozer for Servers: Testing AMD's "Interlagos" Opteron 6200 Series
by Johan De Gelas on November 15, 2011 5:09 PM ESTMeasuring Real-World Power Consumption, Part One
The Equal Workload (EWL) version of vApus FOS is very similar to our previous vApus Mark II "Real-world Power" test. To create a real-world “equal workload” scenario, we throttle the number of users in each VM to a point where you typically get somewhere between 20% and 80% CPU load on a modern dual CPU server. The amount of requests is the same for each system, hence "equal workload".
The CPU Load on the Opteron 6276 looked like this:
The CPU load is typically around 30-50%, with peaks up to 65%. At the end of the test, we get to a low 10%, which is ideal for the machine to boost to higher CPU clocks (Turbo) and race to idle. First we check out the response times.
| vApus FOS Response times (ms) | ||||||||
| CPU | PhpBB1 | PHPBB2 | MySQL OLAP | Zimbra | ||||
| AMD Opteron 6276 | 134 | 47 | 3.6 | 44 | ||||
| AMD Opteron 6174 | 118 | 41 | 3.8 | 45 | ||||
| Intel Xeon X5670 | 76 | 27 | 2.2 | 28 | ||||
ESXi and our Interlagos "Opteron" probably don't understand each other fully, given the newness of the architecture. Some extensive monitoring with ESXtop shows that the lower CPU load is spread among all the cores, and the result is that the Opteron 6276 never reaches its highest clock speed (3.2GHz). That helps make the response times significantly higher than on the Xeon, although they are acceptable. Again, the Interlagos Opteron fails to really beat the "Magny-cours" Opteron.
Our main focus of this benchmark is of course energy consumption.
The Xeon consumes 25% less power, and the older Opteron about 10% less. The performance/Watt ratio of the newest Opteron looks rather bad when running on top of ESX. We shall delve into this deeper in the next several pages.
Facebook
Twitter
RSS
106 Comments
View All Comments
Kevin G - Tuesday, November 15, 2011 - link
I'm curious if CPU-Z polls the hardware for this information or if it queries a database to fetch this information. If it is getting the core and thread count from hardware, it maybe configurable. So while the chip itself does not use Hyperthreading, it maybe reporting to the OS that does it by default. This would have an impact in performance scaling as well as power consumption as load increases.MrSpadge - Tuesday, November 15, 2011 - link
They are integer cores, which share few ressources besides the FPU. On the Intel side there are two threads running concurrently (always, @Stuka87) which share a few less ressources.Arguing which one deserves the name "core" and which one doesn't is almost a moot point. However, both designs are nto that different regarding integer workloads. They're just using a different amount of shared ressources.
People should also keep in mind that a core does not neccessaril equal a core. Each Bulldozer core (or half module) is actually weaker than in Athlon 64 designs. It got some improvements but lost in some other areas. On the other hand Intels current integer cores are quite strong and fat - and it's much easier to share ressources (between 2 hyperthreaded treads) if you've got a lot of them.
MrS
leexgx - Wednesday, November 16, 2011 - link
but on Intel side there are only 4 real cores with HT off or on (on an i7 920 seems to give an benefit, but on results for the second gen 2600k HT seems less important)where as on amd there are 4 cores with each core having 2 FP in them (desktop cpu) issue is the FPs are 10-30% slower then an Phenom cpu clocked at the same speed
anglesmith - Tuesday, November 15, 2011 - link
which version of windows 2008 R2 SP1 x64 was used enterprise/datacenter/standard?Lord 666 - Tuesday, November 15, 2011 - link
People who are purchasing SB-E will be doing similar stuff on workstations. Where are those numbers?Kevin G - Tuesday, November 15, 2011 - link
Probably waiting in the pipeline for SB-E base Xeons. Socket LGA-2011 based Xeon's are still several months away.Sabresiberian - Tuesday, November 15, 2011 - link
I'm not so sure I'd fault AMD too much because 95% of the people that their product users, in this case, won't go through the effort of upgrading their software to get a significant performance increase, at least at first. Sometimes, you have to "force" people to get out of their rut and use something that's actually better for them.I freely admit that I don't know much about running business apps; I build gaming computers for personal use. I can't help but think of my Father though, complaining about Vista and Win 7 and how they won't run his old, freeware apps properly. Hey, Dad, get the people that wrote those apps to upgrade them, won't you? It's not Microsoft's fault that they won't bring them up to date.
Backwards compatibility can be a stone around the neck of progress.
I've tended to be disappointed in AMD's recent CPU releases as well, but maybe they really do have an eye focused on the future that will bring better things for us all. If that's the case, though, they need to prove it now, and stop releasing biased press reports that don't hold up when these things are benched outside of their labs.
;)
JohanAnandtech - Tuesday, November 15, 2011 - link
The problem is that a lot of server folks buy new servers to run the current or older software faster. It is a matter of TCO: they have invested a lot of work into getting webapplication x.xx to work optimally with interface y.yy and database zz.z. The vendor wants to offer a service, not a the latest technology. Only if the service gets added value from the newest technology they might consider upgrading.And you should tell your dad to run his old software in virtual box :-).
Sabresiberian - Wednesday, November 16, 2011 - link
Ah I hadn't thought of it in terms of services, which is obvious now that you say it. Thanks for educating me!;)
IlllI - Tuesday, November 15, 2011 - link
amd was shooting to capture 25% of the market? (this was like when the first amd64 chips came out)