Intel Xeon 3.6 2MB vs AMD Opteron 252 Database Test
by Jason Clark & Ross Whitehead on February 14, 2005 8:00 AM EST- Posted in
- IT Computing
SQL Stress Tool Benchmark
Our first benchmark was custom-written in .NET, using ADO.NET to connect to the database. The AnandTech Forums database, which is over 14GB in size at the time of the benchmark, was used as the source database. We'll dub this benchmark tool "SQL Stress Tool" for the purposes of discussing what it does. We have done some updates to the tool since we first used it; it now supports Oracle, and MySQL. We also adjusted the test time for this test and future tests to 20 minutes. The reason for this was to ensure that we used as much memory as possible for future planned 64 bit tests.
Click to enlarge.
SQL Stress allows us to specify the following: an XML based workload file for the test, how long the test should run, and how many threads it should use in which to load the database. The XML workload file contains queries that we want executed against the database, and some random ID generator queries that populate a memory resident array with ID's to be used in conjunction with our workload queries. The purpose of using random ID's is to keep the test as real-world as possible by selecting random data. This test should give us a lot of room for growth, as the workload can be whatever we want in future tests.
Example workload:
Example Random ID Generator:
The workload used for the test was based on every day use of the Forums, which are running FuseTalk. We took the most popular queries and put them in the workload. Functions, such as reading threads and messages, getting user information, inserting threads and messages, and reading private messages, were in the spotlight. Each reiteration of the test was run for 20 minutes, with the first being from a cold boot. SQL was restarted in-between each test that was run consecutively.
The importance of this test is that it is as real world as you can get; for us, the performance in this test directly influences what upgrade decisions we make for our own IT infrastructure.
Facebook
Twitter
RSS
97 Comments
View All Comments
Visual - Thursday, July 7, 2005 - link
the intel board that you used, you listed it as SE7620AF2. there is no such thing though, so is it a typoed SE7520AF2 or a yet unreleased board?kaka - Saturday, February 19, 2005 - link
??,OPteron is better than xeon!!Fluff - Thursday, February 17, 2005 - link
But in future it would be handy to touch upon extra features such as differences in remote management, what happens if a cpu fails, if memory fails is there hotswop. As these probably affect a decision as well as performance.I believe that people benefit from the sort of technical analysis and simulated real world that Anandtech does but in addition the other factors such as up-time and manangement would be nice to know.
If a cpu fan / stick of memory fails on a database at the weekend and no one is there to hear the alarm what do the various platforms do?
If a cpu fails on a dual opteron does that mean it loses all the data attached to that cpu? Does the same happen on a xeon? Will a Xeon keep going with just one - chipkill?
I'm not sure if this is outside the scope of Anandtech.
Jason Clark - Thursday, February 17, 2005 - link
Hans, you are correct in that they wouldn't be using non supported memory. But, since the board was pre-production and at the time of testing there were no "recommended' memory modules, we had to go with what we had. Word is our issues were bios related and a new bios should address it.Cheers
Jason Clark - Thursday, February 17, 2005 - link
Hans, fair enough on the next article we'll include it for those curious.Jason Clark - Thursday, February 17, 2005 - link
Viditor, we tested with 8GB of memory using PAE and AWE support in SQL. When 64bit versions of sql and windows 2003 are ready we'll be all over it.Viditor - Thursday, February 17, 2005 - link
BTW, for some Linux spec results, check these out...http://www.pathscale.com/pr_021505.html
Sun Fire V20z server (2xAMD Opteron processor Model 252, SLES9) with PathScale EKOPath Compiler Suite: SPECfp2000 -- 2036, SPECint_rate2000 -- 40.4, SPECfp_rate2000 -- 46.5.
The Sun Fire V40z server with PathScale EKOPath Compiler Suite (4xAMD Opteron processor Model 852, SLES9): SPECint_rate2000 76.7, SPECfp_rate2000 -- 87.1.
The Sun Fire V20z server (2xAMD Opteron processor Model 250, SLES8): SPECfp_rate2000 37.2.
IBM eServer OpenPower 710 (2x1.65 GHz Power5, Linux): SPECfp_rate -- 40.2.
IBM eServer p5 510 (2x1.65 GHz Power5, AIX): SPECint_rate2000 -- 33, SPECfp_rate2000 -- 43.2
Viditor - Thursday, February 17, 2005 - link
Jason...I see you are retesting the HT, but I haven't seen a comment from you about testing 64bit with large memory (>4GB). Is this something you just aren't prepared to do right now?
Cheers...
Viditor - Thursday, February 17, 2005 - link
"I read viditor comment that said as single"Yup...very sorry prd00...my bad!
"Which is why we aren't going to provide information like that, as it isn't relevant to the target audience or the purpose of the article"
Fair call Jason, but as this is a beta bios, it might be an important data point...
sleepless - "Looking at the configuration you show Opteron 250 with a 252. Did you have a problem getting another 252 Opteron for the test?"
They built 2 test platforms, 1 with dual 250s and 1 with dual 252s...or so I assume (after my last mistake I take nothing for granted)...:-)
sleepless1 - Wednesday, February 16, 2005 - link
Looking at the configuration you show Opteron 250 with a 252. Did you have a problem getting another 252 Opteron for the test?