Gaming Multitasking Scenario

Our gaming multitasking test basically performs all of the tasks from our first Multitasking Scenario, with the exception of DVD Shrink. We have Firefox loaded with all 13 tabs from our new suite test, iTunes is running and playing a playlist, and Newsleecher is downloading headers. We kept Newsleecher in this test simply because it's the best way for us to be able to have a fairly CPU/disk intensive downloading task running in the background while still maintaining some semblance of repeatability. So, replace Newsleecher with BitTorrent or any other resource-consuming downloading that you may be doing and you're good to go. Note that although we refer to Newsleecher as disk intensive, it, like most downloading operations, isn't that disk intensive at all in the grand scheme of things; it just acts as a good real world background task to have running.

Of course, Norton AntiVirus 2004 and Microsoft's AntiSpyware Beta were also running in the background.

First, we ran our Doom 3 benchmark:

Gaming + Multitasking Environment (Doom 3)

It's not surprising to see AMD at the top of the charts in a gaming comparison, but what's truly interesting is that the Athlon 64 X2 4400+ barely loses any performance due to the multitasking going on in the background. The non-loaded X2 4400+ platform runs at 99.6 fps and here, it drops down to 92% of that speed at 92.2 fps. Even the dual core Intel CPUs don't scale that well, with the Pentium Extreme Edition delivering 81% of its single task performance here. The only explanation for the excellent showing by AMD here is the benefits of their dual core architecture over Intel's, and it is a very impressive showing at that.

Next up is Splinter Cell:

Gaming + Multitasking Environment (Splinter Cell: Chaos Theory)

We continue to see an impressive showing by AMD in their dual core performance - there is virtually no performance drop for AMD in this test.

The dual vs. single core comparison is pretty cut and dry. The Athlon 64 X2 4400+ offers nearly twice the performance of the fastest single core Athlon 64 FX.

Gaming + Multitasking Environment (Splinter Cell: Chaos Theory)

Gaming + Multitasking Environment (Splinter Cell: Chaos Theory)

Multitasking Scenario 5: Compiling Final Words


View All Comments

  • KillerBob - Friday, April 22, 2005 - link


    MT Test 1: PEE 1 - X2 0 Very likely scenario
    MT Test 2: PEE 2 - X2 0 Likely scenario
    MT Test 3: PEE 2 - X2 1 So-so scenario
    MT Test 4: PEE 3 - X2 1 Likely scenario
    MT Test 5: PEE 3 - X2 2 Likely scenario
    MT Test 6: PEE 3 - X2 3 Unlikely scenario

    I play a lot of games, but I never have things in the background, as a matter of fact I don't want to have anyting in the background, except for perhaps a big NewsPro download.
  • MrEMan - Friday, April 22, 2005 - link


    Artificial stupidity run rampant?


    Natural deselection (survival of the twitest)?
  • Quanticles - Friday, April 22, 2005 - link

    I vote that 90% of the people on here have no idea what they're talking about... lol Reply
  • erwos - Friday, April 22, 2005 - link

    "It's odd that some picture game developers immediately supporting the PhysX chip as soon as it's available, but think they'll drag their feet to take advantage of another whole CPU core at their disposal."

    It's basically about the implementation differences of the two. You can be relatively certain that PhysX is going to be shipping their chips/cards with libraries that allow game devs to just speed up certain processing with special function calls (ie, calculate_particle_spread()). Multi-threading requires that you design your application from the very start to take advantage of it (mostly - I would wager splitting off the background music to its own thread is reasonably straightforward).

    Game logic doesn't always lend itself to multi-threading, either. If I shoot my gun, I want to hear the sound next. I don't want it to be thrown at the sound thread, where it may or may not execute next. Threading introduces latency, in other words, unless you so tightly bind your threads together that you may as well not use multi-threading.

  • Griswold - Friday, April 22, 2005 - link

    KillerBob, so that makes you a brilliant illiterate, since it's not what the benchmarks say. :) Reply
  • cHodAXUK - Friday, April 22, 2005 - link

    #83 Get a clue, a single core 3500+ is faster than the quivelant Opteron at the same speed. Why? Unregistered memory and tigher memory timinings. ECC memory comes with a 2-4% performance penalty but the big difference comes with the command speed, 2T for the Opteron and 1T 3500+, the AMD64 thrives on lower lower latancies that can make as big as an 10% performance difference and that is BEFORE we start to even think about raising the FSB speed which makes a significant difference to overall system perfomance. 15% is in no way unrealistic with a mild overclock and lower latancies, if you don't believe me then email Anand and ask him. Reply
  • Zebo - Friday, April 22, 2005 - link

    Jep4444 (#89) What do you mean X2's "arent nearly as good as the dual core Opterons"??

    Comming from XS I suspect don't OC very well?

    But they are the same cores as the Opterons are. and with ram should run signifigantly faster.

    Or do you mean buggy? That's easily attibuted to BIOS, IE none released yet so no working BIOS.

    How about a link please.
  • Umbra55 - Friday, April 22, 2005 - link

    The benchmark overviews show "dual opteron 252 (2.6 GHz)" all over the review. I suppose this is single 252 instead of dual?

    Please correct accordingly
  • emboss - Friday, April 22, 2005 - link

    #40 (Doormat):
    You're forgetting that the size of a dual-core is (roughly) double that of a single-core. So, assuming 1000 cores/wafer, 70% defect rate per core, then a single-core wafer (with an ASP of $500) will net AMD 700*500 = $350K.

    The same wafer with dual-cores will produce (approximately) 1000/2 * (0.7)^2 = 245 CPUs. So, to get the same amount of cash per wafer, AMD needs an ASP of $1429, or the second core costing 85% more than the first core.

    Of course, it's not quite this simple ("bad" chips running OK at lower speeds, etc) but it's not entirely unreasonable to see dual-cores with prices ~3 times that of a single core at the same speed grade. Intel is almost dumping (in the economic sense of the word) dual-core chips.
  • saratoga - Friday, April 22, 2005 - link

    "saratoga, waah? There are similarities between C# and C++. While agree it's java'ish as well, it definitely has similarties to c++. One could say c# shaes similarities with c/c/c++.

    read away:


    I'm guessing you're not a c++ programmer ;)

    Anyway, yes they both use c syntax, however thats pretty much irrelevent given that Java also uses c syntax (as does Managed c++ which incidently IS the .net language directly based on c++) and I've never heard anyone call it related to c++. Beyond (some) syntax heritage and the fact that they're both OO langauges, they're very different beasts.

    ""C# is directly related to C and C++. This is not just an idea, this is real. As you recall C is a root for C++ and C++ is a superset of C. C and C++ shares several syntax, library and functionality." Quoted from above.


    Err yeah c++ is mostly a superset of c++. Thats neither here nor there. Just try and use the c/c++ preprocessor in c# and you'll see very quickly what the difference is. Or try using c++ multiple inherritance. You'll find that just because you took java and added operator overloading and made binding static by default, its not c++.

Log in

Don't have an account? Sign up now