Multitasking Scenario 3: Web Browsing

For our final benchmark, we decided to switch things up a bit and keep Firefox as our foreground application while background tasks ran.  To make things even more stressful, we had no less than 12 tabs open in Firefox, with our main tab being IGN's PSP website - which happens to be very Flash heavy. 

The iTunes and Newsleecher tasks from the first test scenario were also present in this one, plus we did the following:

Open Outlook, immediately import 130MB PST file and immediately switch app focus to Firefox.

We then recorded the total time required to import the new PST while Firefox was our foreground application.  The results were very interesting:

Multitasking Performance - Scenario 3

The most surprising is how poorly AMD did in this test. We actually had to exclude them from the graph as it distorted the bar lengths too much. AMD weighed in at over 27 minutes; from actually using the system, it looks like Flash takes a much bigger performance toll on AMD platforms than it does on Intel.  The end result is that the scheduler devoted very little time to the Outlook process, resulting in the import taking an extremely long time. 

Ignoring the AMD outlier, dual core offered serious performance improvements over single core within the Intel realm alone.  The 840 completed the PST import in around 70% of the time of the 3.73EE.  Again, the gap would grow if more tasks were running, or if we were actually interacting with Firefox instead of just sitting there and reading one page (we confirmed this by actually doing it, but it is a little too difficult to do in a repeatable fashion for testing purposes). 

Multitasking Scenario 2: File Compression Dual Core System Impressions
Comments Locked

141 Comments

View All Comments

  • johnsonx - Monday, April 4, 2005 - link

    It looks like AMD better get busy. AMD woke up Intel from it's complacent slumber, and now Intel is going to start eating AMD's lunch. AMD has completely lost the 64-bit advantage, and will now lose whatever dual-core advantage it had by designing Hammer to be dual-core from the start. Prescott may or may not have been designed for dual-core, but it sure seems to work just fine, doesn't it?

    AMD's problem is that it talks about what it's going to do for too long before actually doing it, as if there isn't anything Intel can do about it. Intel surely can do something about it, and definitely has. This may be an obvious consequence of being a much smaller company: AMD doesn't have the resources to get things done as quickly as Intel can (when Intel is sufficiently motivated), but that just means AMD needs to keep their mouths shut for longer. AMD has been relegated to 'me-too' status for technologies they themselves were first with...

    Object lesson for AMD: Intel can beat you to any launch date you set for any technology or feature you think you've got an exclusive on. Intel can then crush you with volume and market presence. It ain't fair... welcome to life.

    AMD's best bet: whatever you set your launch dates to, surprise launch everything 6 months ahead of schedule. That'll only work a couple of times, but it's better than nothing.
  • Klober - Monday, April 4, 2005 - link

    Two separate points here:

    First, I suppose dual-core may not improve single threaded application performance much over a single-core CPU with HT, but shouldn't it increase performance over a single-core CPU w/o HT? I would think it would allow the OS to run on one core while the application runs on the other core, which in theory should increase performance some. Just a thought, as I'm no expert on scheduling and the resources the OS actively requires.

    Second point, a small simple application that may be useful in benchmarking, particularly in multitasking benchmarks, might be Macro Scheduler by MJT Net. It takes very little in the way of resources, and is very easy to program for starting applications, switching between them, taking screenshots, clicking on options and even typing whatever you'd like wherever you'd like. I think it could be a great base for switching between applications and starting processes inside those applications, all in a very repeatable manner. Timing can be down to the 1/10,000th of a second if need be, and using a scheduler with minimal resource impact would take the human element out of the benchmarking. Maybe you've already looked into this, or something similar, but it's just a thought that may make certain benchmarking situations easier for all of you that bring us these great (p)reviews.
  • Googer - Monday, April 4, 2005 - link

    In Soviet Russia you post all you bad jokes Here:
    http://forums.anandtech.com/messageview.aspx?catid...
  • knitecrow - Monday, April 4, 2005 - link

    yo dog, where the temperature at?





    but seriously, in addition to the usual suspects, I think anandtech should have compared pentium D to xenon 3.2ghz just to see the performance difference.

  • johnsonx - Monday, April 4, 2005 - link

    ok, sorry... I posted my comment before reading the encoding benchmarks, where I see you did exactly what I suggested. My bad.
  • vaystrem - Monday, April 4, 2005 - link

    "2) Open iTunes and start playing the latest album of avid AnandTech reader 50 Cent on repeat all."

    ? Really?
  • johnsonx - Monday, April 4, 2005 - link

    I know it's nearly double the number of benchmarks to run, but it would have been instructive to see both Pentium processors benchmarked without HT as well. Testing the dual-core pentium EE without HT would of course mimic a 3.2Ghz Pentium D, and testing the single core P4 without HT would give us a baseline single-core, single execution thread reference.

    Finally, it might also be instructive to benchmark current P4 at 3.2Ghz, again both with and without HT.

    Easy for me to say, I know, since I'm not the one who has to do all the benches....
  • LeadFrog - Monday, April 4, 2005 - link

    I like the theory of if it can't get any faster lets just combine a few.

    SLI, RAID, and Dual Core CPU's.
  • segagenesis - Monday, April 4, 2005 - link

    One site mentioned 125W power consumption. Ow.

    Well, its a start... but I want to see AMDs offering first.
  • msva124 - Monday, April 4, 2005 - link

    This looks promising, I wonder if AMD might eventually cave and implement hyper-threading in their processors, in addition to dual core. Or is that not part of the cross licensing agreeement?

Log in

Don't have an account? Sign up now