Marin Mersenne2^P-1
Username
Password
Forgot password?
Great Internet Mersenne Prime Search
GIMPS
Finding World Record Primes Since 1996

PrimeNet CPU Benchmarks

Log in to see your benchmarks
CPU speed range:
CPU must have this many benchmarks reported:
Only display benchmarks reported since: (yyyy-mm-dd)
Model AMD Athlon(tm) 64 X2 Dual Core Processor 6000+
Stock Speed   3001 MHz
Features Prefetch,3DNow!,SSE,SSE2
L1 Cache 64 KB
L2 Cache 1024 KB

Program Speed (MHz) 29.69M to 34.56M (1792K)34.56M to 39.50M (2048K)39.50M to 49.10M (2560K)49.10M to 58.52M (3072K)58.52M to 68.13M (3584K)68.13M to 77.91M (4096K)Trial fac 65 bitsValid Data?Select
Windows64, Prime95, v28.9, build 2312958.7164.0383.9399.19127.29143.22
Windows64, Prime95, v28.9, build 2312957.0062.7483.2899.15124.39132.36
Windows64, Prime95, v28.9, build 2312957.1263.0684.2498.72123.68132.04
Windows64, Prime95, v28.9, build 2301558.2163.1084.45100.71125.12134.32
Windows64, Prime95, v28.9, build 2301573.22108.0897.39132.69149.06156.07
Windows64, Prime95, v28.5, build 2301359.6564.7585.00102.02126.57136.10
Windows64, Prime95, v28.5, build 2301384.2999.20123.16151.55183.20196.47
Windows64, Prime95, v28.5, build 2301358.7463.5584.12104.77127.30134.82
Windows64, Prime95, v28.7, build 1301358.2762.9283.62101.10125.90133.82
Windows64, Prime95, v28.7, build 1301357.8962.9091.34101.22125.86133.82
Windows64, Prime95, v28.7, build 1301357.8862.9683.60101.27125.71134.34
Windows64, Prime95, v28.7, build 1301389.6994.33129.15155.25207.13193.29
Windows64, Prime95, v28.7, build 1301358.8764.0684.74102.49126.09135.36
Windows64, Prime95, v28.7, build 1301357.9263.0883.72101.39126.79134.02
Windows64, Prime95, v28.7, build 1301363.2971.23115.10115.84140.21152.97
Windows64, Prime95, v28.7, build 1300057.9263.2083.77100.59125.44134.98
Windows64, Prime95, v29.2, build 22999
Windows64, Prime95, v28.9, build 22992100.3191.21119.47144.15178.12201.71
Windows64, Prime95, v28.7, build 1298458.5863.7084.51102.05128.13135.51
Windows64, Prime95, v28.9, build 22984111.7468.60139.37107.49137.96140.45
Windows64, Prime95, v29.3, build 12984
All timings are in milliseconds - lower is better

You can help improve the accuracy of our benchmark data by reporting benchmarks that are obviously wrong. This can happen when cpu speed is detected incorrectly which often occurs when SpeedStep is enabled. Bad data can also occur when other programs run during a benchmark -- you might see all timings are too high or you might see a smaller FFT taking more than a larger FFT. By flagging these bad benchmarks, the main benchmark page will report more accurate average timings.

 Check to confirm you want to mark benchmarks suspect

If someone has inadvertantly marked good benchmark data suspect, you can vote for marking the benchmark valid.

If the stock CPU speed is not set correctly, you can set the stock CPU speed so that we correctly identify overclocked and underclocked benchmarks.

Stock CPU speed: