I dont have the numbers, but Im betting the P4 beat out the K8 in super pi
As long as we're betting nickels in the context of 1M... you lost!
http://www.pcstats.com/articleview.cfm?articleid=1790&page=8. Second chart on the page - 3.2GHz Prescott (1 MB L2) loses to 2.4GHz Venice (512K L2).
On this benchmark forum -
http://www.devhardware.com/forums/benchmarking-tools-23/hwbot-superpi-1m-ranking-93516.html - we can roughly gauge the clock efficiency of various architectures at Pi calculation by multiplying MHz by seconds to yield "million clock cycles to calculate 1M" (lower is better efficiency). I added various results from other sources (e.g. http://www.devhardware.com/forums/benchmarking-tools-23/devhardware-super-pi-42201.html) to round out the timelines, as this benchmark is very easy to replicate, though different versions and lower level memory settings can slightly affect times:
Athlon Thunderbird @ 1400 MHz: 104s (145600 MHz-s)
AthlonXP Palomino @ 1400 MHz: 79s (110600 MHz-s)
AthlonXP Barton @ 2656 MHz: 38.2s (101500 MHz-s)
Athlon64 San Diego @ 3180 MHz: 27.1s (86200 MHz-s)
Athlon64x2 Toledo @ 2864 MHz: 29.9s (85600 MHz-s)
Athlon64x2 Brisbane @ 3343 MHz: 26.3s (87900 MHz-s)
Phenom 9950 @ 3905 MHz: 19.9s (77700 MHz-s)
[Phenom WR result from http://www.xtremesystems.org/forums/showthread.php?t=206289]
Deneb @ 2801-3441 MHz: 25.1-20.5s (70-71000 MHz-s) [http://www.tcmagazine.com/comments.php?id=20790&catid=2.]
Pentium4 1.6A @ 1600MHz: 105s (168000 MHz-s)
Pentium4 Northwood @ 3590 MHz: 39.3s (141100 MHz-s)
Pentium4 Prescott @ 3980 MHz: 32.8s (130500 MHz-s)
Pentium4 Presler @ 4269 MHz: 31.4s (134000 MHz-s)
Pentium II Deschutes @ 504 MHz: 235s (118400 MHz-s)
Pentium III Coppermine @ 597 MHz: 194s (115800 MHz-s)
Pentium M Banias @ 1400 MHz: 76.1s (106540 MHz-s)
Pentium M Dothan @ 2949 MHz: 25.1s (
74000 MHz-s)
Core Duo @ 2900 MHz: 20.6s (
59700 MHz-s)
Core 2 Duo Conroe @ 4100 MHz: 12.5s (51250 MHz-s)
Core 2 Duo Penryn @ 4600 MHz: 10.4s (47800 MHz-s)
Nehalem C0 @ 5313 MHz: 7.75s (41200 MHz-s) [Fugger's recent accomplishment]
Atom @ 1600 MHz: 92.9s (148600 MHz-s)
So for SuperPi and quite a few other apps, Intel made a clock-efficiency champion out of its Pentium M line, which I remember grounded its notebook market dominance but was mostly irrelevant on the desktop because clocks were designed
not to scale. Intel made some gigantic leaps in pi-calculating efficiency with a couple mobile generations. Then the breakout happened when Core 2 Duo simultaneously increased marginal efficiency and greatly increased operable frequency, leaving older architectures distantly behind on this benchmark.
AMD, on the other hand, didn't experience a huge clock-efficiency leap like the Pentium M, and many of its die shrinks were also uneventful at the core and thus insignificant impacts on SuperPi efficiency (e.g., Sledgehammer to San Diego to Toledo to Brisbane).
Though certainly not the only factor, SuperPi generally favors decent amounts of fast cache; particularly where cache is slow and/or reduced, I notice SuperPi times go up.