Development Performance - Compiling Firefox

Our Quake 3 compile test was getting a bit long in the tooth, so we're introducing a brand new test: compiling Firefox. We followed the instructions diagramed here.

Firefox Build

This particular test is only single threaded, and so we see that the fast single core CPUs take the lead. Intel's performance in this compiling test, as always is the case with our compiling benchmarks, is not up to par with AMD.

The Real Test - AnandTech's Multitasking Scenarios

Before our first dual core articles, we asked for feedback from the readers with regards to their multitasking usage patterns. Based on this information, we formulated some of our own benchmarks that would stress multitasking performance. We've already gone over the impacts of dual core CPUs on subjective interactions, so we'll just point you back to previous articles for our take on that if you haven't read them already. In the end, we know that dual core CPUs make our systems much more responsive and provide the same sort of smooth operation that SMP systems have done for years. But, the question now is: who has better multitasking performance? AMD or Intel? And that's exactly what we're here to find out.

We started with a test bed configured with a number of fairly popular applications:
Daemon Tools
Norton AntiVirus 2004 (with latest updates)
Firefox 1.02
DVD Shrink 3.2
Microsoft AntiSpyware Beta 1.0
Newsleecher 2.0
Visual Studio .NET 2003
Macromedia Flash Player 7
Adobe Photoshop CS
Microsoft Office 2003
3ds max 7
iTunes 4.7.1
Trillian 3.1
DivX 5.2.1
AutoGK 1.60
Norton Ghost 2003
Adobe Reader 7
Cygwin
gcc
mingw
Doom 3
Splinter Cell: Chaos Theory
What's important about this list is that a handful of those programs were running in the background at all times, primarily Microsoft's AntiSpyware Beta and Norton AntiVirus 2004. Both the AntiSpyware Beta and NAV 2004 were running with their real time protection modes enabled, to make things even more real world.

3D Rendering Multitasking Scenario 1: DVD Shrink
Comments Locked

144 Comments

View All Comments

  • KillerBob - Friday, April 22, 2005 - link

    Griswold,

    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

    102,

    Artificial stupidity run rampant?

    or

    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
  • 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.

    -Erwos
  • Griswold - Friday, April 22, 2005 - link

    KillerBob, so that makes you a brilliant illiterate, since it's not what the benchmarks say. :)
  • 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.
  • 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:

    http://www.mastercsharp.com/article.aspx?ArticleID...

    http://www.csharphelp.com/archives/archive138.html

    "

    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.

    L8r."

    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