First off, in light of TaPaKaH's recent admittance of faking everything, we're not scheming to get anyone, or anything like that. He did on his own. However, let's put that in perspective as well. We were all fooled for MONTHS. That's how possible, legitimate, and prevalent cheating really is....and it's a shame.
In zbogorgon's recent thread:
http://www.xtremesystems.org/forums/...d.php?t=125972 , he further elucidates how cheating can be done easily....he's due a lot of credit for coming forward and bringing this up, as well as recognizing where some cheating may exist.
Let's remember one key thing here....the methods that we know exist, speedhack linearly.
Well, SPi doesn't scale linearly, it's inversely proportional. You can't linearly generalize: 100MHz increase is equal to a given time decrease. However, you can say this: MHz * time ~= X, where X is constant for any given setup.
For a high speed, VERY well tweaked 975X + Conroe sytem, X is equal to about 50500. Remember this.
Let's take a look at some top SPI 1.5 results, taken from hwbot.org and from on the forum.
OPB - 5550 x 8.91 = 49451 (Oct 16)
here
OPB - 5567 x 9.16 = 50994 (Oct 10) **
Maxxxpct - 5506 x 9.33 = 51370
Coolaler - 5525 x 9.00 = 49725 Lookie here
TaPaKaH - 5408 x 9.36 = 50619
OPB - 5407 x 9.39 = 50772 (Sept 24) **
Memoryextreme Team - 5348 x 9.44 = 50485
Hipro5 - 5376 x 9.45 = 50803
OPB - 5329 x 9.55 = 50892 (Sept 8) **
ojdr2001 - 5348 x 9.55 = 51073
OPB - 5305 x 9.63 = 51087 (Sept 2) **
KP - 5297 x 9.68 = 51275
Hipro - 5217 x 9.72 = 50709
TaPaKaH - 5208 x 9.78 = 50934
zbogorgon - 5196 x 9.8 = 50920
hipro - 5138 x 9.89 = 50815
Kyosen - 4167 x 12.05 = 50212 Lookie here. FWIW, this is THE BEST clock-for-clock time to be found...that's legit at least
before - 5000 x 10.06 = 50300 Lookie here...look at that RAM speed!
kyosen - 9.937 x 5086 = 50540
Lookie here
See a trend? Known, reputable SuperPi GODS need lowish MHz, insane tweaks, and insane RAM to barely break below 50400.
Let's now take a look at Coolaler's progression, from slowest to fastest:
5200 x 9.72 = 50544 (July 12)
here
5300 x 9.64 = 51092 (July 17)
here
5396 x 9.485 = 51181 (July 18)
here
5409 x 9.484 = 51299 (July 19)
here
Now things begin to get funky
5485 x 9.204 = 50484 (July 23) here
5512 x 9.156 = 50468 (July 28) here
Now the grand finale:
5525 x 9.000 = 49725 (Aug 2) here
Not a single one of those final three has outstanding FSB/RAM speed or timings, not a single one has much headroom for MHz suicide stability....and are EXCEEDINGLY fast, especially considering his tweaking skills. Something changed....something we can't see.
Well, let's take a look at his results from above....see clock-for-clock improving over time? Then he drops the bomb: 8.906 at 5550. He also later shares all his tweaks, they're old, they don't do that much (if anything) on C2D, people have tried them. Then, if you also look back at his non-WR results, you see this gem:
4710 x 10.344 = 48720 here
....which is just crazy fast, fast to the point where he probably ran it at a higher speed than what he had in the screenshot.
Anyway, something's up with the orange and red results....they're just not legit. The green results are the best we could find....and are by known SPI legends, and have the hardware setting to backup the clock-for-clock greatness they have.
Looking at the top 250 results between hwbot.org and Coolaler and OPB's posts, and charting them in excel....well, pictures certainly can say a thousand words.

Quick explanation: each point represents a SPI run, look at the axis to tell what each graph is graphing....the "average" line is, based on the top 250 results and their clock-for-clock performance, that is the "average expected performance line". The "ideal" line is based on "50500"....a.k.a., a VERY well-tweaked system, and what you can expect as MHz changes.
Coolalers and OPB's results have been singled out so you can tell which are theirs. Picoo's recent run is also singled out as the new WR, and to show, that what is expected from an insanely tuned system from one of Team Japan's members.
Some sort of explanation is due....either it's a bug, a cheat, or a tweak that does what no other tweak can do in 1M: improve times by more than a few hundreths of a second.