Overclocking to Save the Day?

Of course, the big question is - "What if you overclock it?"

As you can expect, the Pentium M benefits greatly from being overclocked; not necessarily from the CPU being overclocked, but from the memory bus being overclocked. Unfortunately, as we mentioned before, the 855GME chipset and the two motherboards that we have based on it don't seem to want to overclock the memory bus too much, so we're left with somewhat nice performance gains from overclocking, but not ideal.

The problem with overclocking just the Pentium M is that it paints a skewed picture of reality - as comparing one overclocked processor to a ton of stock-clocked CPUs isn't really fair. But folks are always interested to see what an overclocked Pentium M can do, so we're here to show it off.

The beauty of the current Dothan based Pentium M CPUs is that they are 90nm chips, but without the heat issues of the Prescott based Pentium 4, meaning that they should overclock reasonably well. And overclock they do - our 2.0GHz sample easily hit 2.40GHz (133MHz x 18), and our 1.7GHz samples had no troubles getting up to 2.0GHz (one even hit 2.26GHz). We'd see bigger performance gains if we could bump up the memory clock beyond the 355MHz (to which we were limited), but that will most likely have to wait for new motherboards/chipsets.

Here are some abridged performance results with the overclocked Pentium M included:

Overclocking: Discreet 3ds max 6 (OpenGL) - SPECapc Rendering Composite

Overclocking: Doom 3

Overclocking: DivX 5.2.1 Encoding Performance

Overclocking: Visual Studio 6 Compiler Performance

Overclocking: WinRAR 3.40 Archiving Performance

Overclocking: Business Winstone 2004

Overclocking: Multimedia Content Creation Winstone 2004

Overclocking: SPECviewperf 8 - 3dsmax 3.1 Performance

Overclocking: SPECviewperf 8 - CATIA V5R12 Performance

Overclocking: SPECviewperf 8 - Lightscape Visualization System Performance

Overclocking: SPECviewperf 8 - Maya V5 Performance

Overclocking: SPECviewperf 8 - Pro/ENGINEER Performance

Overclocking: SPECviewperf 8 - Solidworks 2004 Performance

Overclocking: SPECviewperf 8 - Unigraphics V17

Workstation Applications Price based Performance Comparison
Comments Locked

77 Comments

View All Comments

  • bobsmith1492 - Monday, February 7, 2005 - link

    Granted the T8000 here is an Intel fanboy, but please notice Anand was comparing clock-for-clock.
  • T8000 - Monday, February 7, 2005 - link

    There is one big difference between this review and the reviews where the Pentium M did very well: CLOCKSPEED!

    While others where able to get over 2.8 Ghz with aircooling, Anand got just 2.4 Ghz. This may be a coincidence, but it is the difference between surprisingly good performance and a few % below others.

    As most of the benchmarks where based on the stock 2 Ghz, the difference became even greater.

    So this review just shows that the stock speed Pentium M performs about 30% less with about 30% less clockspeed than overclocked versions.

    A slightly redesigned version with higher voltages is not extremely unlikely to hit at least 3 Ghz. Combining that with a desktop chipset will result in stellar performance, as the benchmark scores in this review (x1.5) indicate.

    But since there is no slightly redesigned version and Intel has no good reason to make one, the current Pentium M desktops will only appeal to overclockers and silent computing people.

    Also, for some reason, Anand found the 90W TDP of the 2.4 Ghz A64 closer to the 20W of the P-M than to the 110W of the 3.8 Ghz P4.
  • CSMR - Monday, February 7, 2005 - link

    That's a very good option Zebo, thanks for posting it.
  • teutonicknight - Monday, February 7, 2005 - link

    One suggestion: Why don't you start using a newer version of Premiere for testing? I personally don't use it, but every that I know who does says before Premiere Pro, the program sucked. I'm sure the render results would be much more realistic and accurate if you used a more up to date version of the program
  • Regs - Monday, February 7, 2005 - link

    I was wondering the same thing too Jeff. If you feed it more bandwidth, it would eliminate the pipeline stalls and maybe give it a chance to reach higher clock speeds. Right? Or is it still prohibited by the shorter pipeline to reach higher clock speeds?

    Longer pipeline = wasted clock cycles. But to me that sounds like the PM should actually scale a lot better with a speed boost. Why exactly does it scale badly compared to a P4? Could it be remedied in anyway with a dual channel memory bus?
  • ozzimark - Monday, February 7, 2005 - link

    there's something wrong with the 3400+ in the spec tests. why is the 3000+ beating it consitantly?
  • Warder45 - Monday, February 7, 2005 - link

    Maybe I missed something but I don't see the reason for all the negitivity in the final words. The 2.4Ghz P-M was very close to the A64 2.4Ghz in many of the tests, 3D rendering seemed to slow it down but that looked like it. With better boards and memory the P-M might best the A64 in a clock for clock match up.

    I do agree the prices are way too high. I think Intel really needs to wake up and smell what they have cooking here. With more support and more aggressive priceing they could easily have a winner in the HTPC and SFF markets.
  • plewis00 - Monday, February 7, 2005 - link

    Surely when someone builds a mainboard with the Sonoma (i915) platform using PCI-E and DDR2-533 then it will change. And I wouldn't have thought that's that far off assuming they don't charge rip-off prices for the technology. It would also be perfect for Shuttle systems where the emphasis is on quietness and coolness rather than so much on performance.
  • Zebo - Monday, February 7, 2005 - link

    CSMR
    So's this one very soon..
    http://www.xtremesystems.org/forums/showthread.php...

    ...more than excellent performance wise if Dothan is excellent...power differential hopefully for AMD will be nominal.
  • Sokaku - Monday, February 7, 2005 - link


    While it is true that the A64 has way more bandwidth, I doubt that is the reason why it crushed the P-M in the Professional Applications. I think the real cause is to be found in the P-M's abillity to do FP divisions. The P-III had a pipelined FP unit, however div operations were extremly expensive. My guess would be that Intel haven't thrown much effort into improving on this.

Log in

Don't have an account? Sign up now