Data Warehouse Test Explained

We are always looking to improve the quality of our reviews and as a result, we have added a new Stress Test to our suite.

This "Data Warehouse" test is focused on large record sets with plenty of aggregation. This test is based on a system that we developed to track and manage Request statistics for www.AnandTech.com and Forums.AnandTech.com. It tracks statistics like Requests/Hour, Requests/Hour/IP Address, Unique IP Addresses/Hour, Unique Users/Hour, Daily Browser stats, etc. These stats are further summarized by site, i.e.: www or Forums.

As with the other Stress Tests, each test was repeated three times and the average between the three tests was used. For this Data Warehouse Stress Test, we defined a quantity of work to complete and measured how long each platform required to process the workload.

So, to ensure that IO was not the bottleneck, each test was started with a database, including tempdb, which had already been expanded so that autogrow activity did not occur during the test. During the execution of the tests, there were no applications running on the server or monitoring software. Task Manager, Profiler, and Performance Monitor where used when establishing the baseline for the test, but never during execution of the tests.

At the beginning of each platform, the server was rebooted to ensure a clean and consistent environment. The database was always copied to the 8 disk RAID 0 array with no other files present to ensure that file placement and fragmentation was consistent between runs. In between each of the three tests, the database was deleted, the original database was copied again to the array, and SQL Server was restarted.

There is no "client" required for this test. The workload is initiated by a stored procedure call from Query Analyzer.


"Order Entry" Stress Test results Data Warehouse results
Comments Locked

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?

Log in

Don't have an account? Sign up now