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:


    Select1
    select count(iuserid) as usercount from ftdb_forumusers where iforumid = 1


    Select2
    select count(u.iuserid) as currusercount from ftdb_users u,ftdb_forumusers fu where fu.iforumid = 1 and u.iuserid = fu.iuserid and dtlastvisiteddate > '[q]qGetLastVisitDate[/q]'

Example Random ID Generator:


    qGetLastVisitDate
    select dtlastvisiteddate,newid() as ldate from ftdb_users where dtlastvisiteddate is not null order by ldate


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.


Test hardware configuration SQL Stress Results
Comments Locked

97 Comments

View All Comments

  • Hans Maulwurf - Wednesday, February 16, 2005 - link

    Yes, but IBM would not use memory that is not on the recommanded list of the mainboard, at lest I hope so.
    And it is possible that the boad sets very high latencies for the memory you used. So I think it is an important information especially when using memory that is not recommanded.
  • Jason Clark - Wednesday, February 16, 2005 - link

    Hans, let me ask you this. When someone in an IT dept. calls Compaq, Dell, HP or IBM for a server do you think they ask them what the memory timings are set at? The answer is no. 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. We're trying to educate the IT folks on what platform does what on certain workloads and IT related tests.

    Cheers.
  • prd00 - Wednesday, February 16, 2005 - link

  • Hans Maulwurf - Wednesday, February 16, 2005 - link

    Jason,

    you do not have to play with the memory timings to report them.
  • dm - Tuesday, February 15, 2005 - link

    danidentity, i guess you're right when you mentioned about 5pages of reply ;)...
  • prd00 - Tuesday, February 15, 2005 - link

    Sorry, missed your comment Jason.. I read viditor comment that said as single. So, in Dual setup, Xeon is more powerful now ;). Then, Xeon must be faster in single.
    I am waiting for 64 bit one ;)
  • prd00 - Tuesday, February 15, 2005 - link

    Wow.. single??
    On single setup, I already knew that Xeon is powerful. Right now what we are lacking is a TRUE SERVER BENCHMARK. Not just single vs single. I can safely recommend Xeon since a few months ago on single setup, but right now, most of our customers are asking about DUAL SETUP. Some are looking in QUAD setup. Single is useless in server environment. For databse server, 9 out of 10 are looking for 2p setup
    So, what I am really looking are database benchmark on single, dual and quad setup, and also how does it scale. Which platform best suited for 2p and 4p, and which one has better upgrade future (i.e. by adding processors), and until what point.

    So, like, Xeon is good for 1p, but on 2p Opteron is better, while more than 8p we can consider Itanium instead for database server.

    Kind of conclusion like that.
  • Jason Clark - Tuesday, February 15, 2005 - link

    Zebo, because this is a server test. You don't play with memory timings/overclocking in servers. We used default memory timings that the Tyan board set for the memory. I linked to the manufacturer specs on the memory which identifies its SPD rating. The only thing we're investigating at this point is the 1GHz HT issue in the bios.
  • PrinceGaz - Tuesday, February 15, 2005 - link

    It's certainly a change from the usual Opteron beating Xeon in almost all server tests reviews, and all the more so because you say they were both dual CPU systems (I was under the impression while reading they were only single CPU servers being compared).

    It just goes to show how much difference the benchmarks that are run, how well the systems are set up, and any other things we never know about, can influence results.

    I'm glad Intel is coming out ahead in some tests on AT, maybe you should make them come out ahead on desktop stuff too as that might encourage AMD to drop the prices on the higher rated E0 revision Athlon 64 processors sooner rather than later :)
  • Zebo - Tuesday, February 15, 2005 - link

    Jason how comw you did'nt say mem timings nor speed or if 1T or not? I've never seen a review from AT without this.

Log in

Don't have an account? Sign up now