The Best Server CPUs part 2: the Intel "Nehalem" Xeon X5570
by Johan De Gelas on March 30, 2009 3:00 PM EST- Posted in
- IT Computing
| Decision Support: Nieuws.be | |
| Operating System | Windows 2008 Enterprise RTM (64-bit) |
| Software | SQL Server 2005 Enterprise x64 SP3 (64-bit) |
| Benchmark software | vApus + real world "Nieuws.be" Database |
| Database Size | > 100 GB |
| Typical error margin | 1-2% |
The Flemish/Dutch Nieuws.be site is one of the newest web 2.0 websites, launched in 2008. It gathers news from many different sources and allows readers to personalize their view of all this news. The Nieuws.be site sits on top of a large database - more than 100GB and growing. This database consists of a few hundred separate tables, which have been carefully optimized by our lab (the Sizing Servers Lab).
Nieuws.be allowed us to test the MS SQL 2005 database for CPU benchmarking. We used a log taken between 10:00 and 11:00, when traffic is at its peak. vApus, the stress testing software developed by the Sizing Servers Lab, analyzes this log and simulates real users by performing the actions they performed on the website. In this case, we used the resulting load on the database for our test. 99% of the load on the database consists of selects, and about 5% of them are stored procedures. Network traffic is 6.5MB/s average and 14MB/s peak, so our Gigabit connection still has a lot of headroom. DQL (Disk Queue Length) is at 2 in the first round of tests, but we only report the results of the subsequent rounds where the database is in a steady state. We measured a DQL close to 0 during these tests, so there is no tangible impact from the hard disks. This test is as real world as it gets! All servers were tested in a dual CPU configuration.
Seven times faster than a 3-year old CPU and 76% faster than an adversary that used to outperform almost every Intel CPU! Nehalem is like a CPU that used a time machine and teleported to 2009 from 2011. To put this kind of performance into perspective: it would take a 4.7GHz Opteron to keep up with Nehalem at 3.03GHz (that's the average clock speed as Turbo mode was enabled).
Facebook
Twitter
RSS
44 Comments
View All Comments
gwolfman - Tuesday, March 31, 2009 - link
Why was this article pulled yesterday after it first posted?JohanAnandtech - Tuesday, March 31, 2009 - link
Because the NDA date was noon in the pacific zone and not CET. We were slightly too early...yasbane - Tuesday, March 31, 2009 - link
Hi Johan,Any chance of some more comprehensive Linux benchmarks? Haven't seen any on IT Anandtech for a while.
cheers
JohanAnandtech - Tuesday, March 31, 2009 - link
Yes, we are working on that. Our first Oracle testing is finished on the AMD's platform, but still working on the rest.Mind you, all our articles so far have included Linux benchmarking. All mysql testing for example, Stream, Specjbb and Linpack.
Exar3342 - Monday, March 30, 2009 - link
Thanks for the extremely informative and interesting review Johan. I am definitely looking forward to more server reviews; are the 4-way CPUs out later this year? That will be interesting as well.Exar3342 - Monday, March 30, 2009 - link
Forgot to mention that I was suprised HT has such an impact that it did in some of the benches. It made some huge differences in certain applications, and slightly hindered it in others. Overall, I can see why Intel wanted to bring back SMT for the Nehalem architecture.duploxxx - Monday, March 30, 2009 - link
awesome performance, but would like to see how the intel 5510-20-30 fare against the amd 2378-80-82 after all that is the same price range.It was the same with woodcrest and conroe launch, everybody saw huge performance lead but then only bought the very slow versions.... then the question is what is still the best value performance/price/power.
Istanbul better come faster for amd, how it looks now with decent 45nm power consumption it will be able to bring some battle to high-end 55xx versions.
eryco - Tuesday, April 14, 2009 - link
Very informative article... I would also be interested in seeing how any of the midrange 5520/30 Xeons compare to the 2382/84 Opterons. Especially now that some vendors are giving discounts on the AMD-based servers, the premium for a server with X5550/60/70s is even bigger. It would be interesting to see how the performance scales for the Nehalem Xeons, and how it compares to Shanghai Opterons in the same price range. We're looking to acquire some new servers and we can afford 2P systems with 2384s, but on the Intel side we can only go as far as E5530s. Unfortunately there's no performance data for Xeons in the midrange anywhere online so we can make a comparison.haplo602 - Monday, March 30, 2009 - link
I only skimmed the graphs, but how about some consistency ? some of the graphs feature only dual core opterons, some have a mix of dual and quad core ... pricing chart also features only dual core opterons ...looking just at the graphs, I cannot make any conclusion ...
TA152H - Monday, March 30, 2009 - link
Part of the problem with the 54xx CPUs is not the CPUs themselves, but the FB-DIMMS. Part of the big improvement for the Nehalem in the server world is because Intel sodomized their 54xx platform, for reasons that escape most people, with the FB-DIMMs. But, it's really not mentioned except with regards to power. If the IMC (which is not an AMD innovation by the way, it's been done many times before they did it, even on the x86 by NexGen, a company they later bought) is so important, then surely the FB-DIMMs are. They both are related to the same issue - memory latency.It's not really important though, since that's what you'd get if you bought the Intel 54xx; it's more of an academic complaint. But, I'd like to see the Nehalem tested with dual channel memory, which is a real issue. The reason being, it has lower latency while only using two channels, and for some benchmarks, certainly not all or even the majority, you might see better performance by using two (or maybe it never happens). If you're running a specific application that runs better using dual channel, it would be good to know.
Overall, though, a very good article. The first thing I mention is a nitpick, the second may not even matter if three channel performance is always better.