ABOUT BENCH FORUMS PODCAST LOGIN REGISTER
PC Components
Smartphones & tablets
Systems
ENTERPRISE & IT
GUIDES

AMD's dual core Opteron & Athlon 64 X2 - Server/Desktop Performance Preview

 by Anand Lal Shimpi, Jason Clark & Ross Whitehead on April 21, 2005 9:25 AM EST
144 Comments | Add A Comment
144 Comments

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.

Web Tests - FuseTalk .NET SQL Stress Results
PRINT THIS ARTICLE
Comments Locked

144 Comments

View All Comments

  • Zebo - Friday, April 22, 2005 - link

    It's all good Jep. I was mainly hoping you'd link me to a real live X2 over at xtreme which is why I persisted;)

  • Minotar - Friday, April 22, 2005 - link

    All I can say is WOW!!! AMD keeps kicking more and more ass!!!!!!

  • Jep4444 - Friday, April 22, 2005 - link

    why would i make this up? im just saying what i was told, for all i know that person made it up

    PS if anyone tries to comment and i dont respond within the next 3 days, its cause i wont be on, not cause im backing out of what i said

  • Zebo - Friday, April 22, 2005 - link

    Frankey Jep I'm not buying it. It would cost AMD signifigantly more to make these dual 1MB L2 cores different at the core level. 8XX, 2XX, 1XX, and X2 are identical except for tracing in the pakageing and pins to make them function differently. Check out Tomshardware's recent CPU article about AMD manufacturing and you'll see what I'm talking.

  • Jep4444 - Friday, April 22, 2005 - link

    im not trying to start a rumour, im very much pro AMD(and if you knew me, i generally dislike attention)

    all im saying is dont decided it'll be so fast until we see the real thing

  • Son of a N00b - Friday, April 22, 2005 - link

    #107......rumor.....looking for attentin....engineering sample...of course rushed....BIOS........shhhh jep...........period

    :-P

  • Filibuster - Friday, April 22, 2005 - link

    If you've actually read through this entire thing, congratulations!

  • Jep4444 - Friday, April 22, 2005 - link

    #98 what i heard is from word of mouth, not from the site itself

    while it is true they don't OC very well, apparently the Athlon X2 was rushed and so its functionality wasn't as good as the Opteron 875

    from what i hear they don't multi-task nearly aswell as the Opteron does but single threaded performance should still be up to par

    the Athlon 64 has had changes made to the ALU amongst other places which would differentiate it from the Opteron aswell

    keep in mind i have no actual proof of this and i would love to be wrong but the guys at XS generally know what they're talking about

  • UzairH - Friday, April 22, 2005 - link

    AT should run the doom 3 tests again, this time not using the timedemo but actual gameplay run-throughs. If Doom3 uses a seperate thread for physics then dual-core should definitely benefit.

  • fitten - Friday, April 22, 2005 - link

    #102 ++
Copyright © 2024. All rights reserved.
BENCH
TOPICS
FOLLOW
ABOUT

Log in

Don't have an account? Sign up now