Marin Mersenne 2^P-1
Username
Password
Forgot password?
Blue
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 Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
Stock Speed   3000 MHz
Features Prefetch,SSE,SSE2,SSE4
L1 Cache 32 KB
L2 Cache 6144 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.7, build 1301029.0230.4338.1448.0257.6167.69
Windows64, Prime95, v29.8, build 63010
Windows64, Prime95, v28.7, build 1300733.3933.8446.2248.6760.5267.06
Windows64, Prime95, v28.9, build 2300529.2735.0639.9349.2959.0065.40
Windows64, Prime95, v28.10, build 1300527.2829.2736.8546.5755.2460.72
Windows64, Prime95, v28.10, build 1300527.2129.9837.9247.4557.4163.20
Windows64, Prime95, v29.4, build 83005
Windows64, Prime95, v29.3, build 13004
Windows64, Prime95, v28.7, build 1300026.8631.1237.8747.5855.1160.44
Windows64, Prime95, v28.9, build 2300027.7730.2537.9447.4356.6463.41
Windows64, Prime95, v28.7, build 1300064.6946.3589.1372.4387.7096.64
Windows64, Prime95, v28.10, build 1299926.2129.5037.3645.9053.7458.74
Windows64, Prime95, v28.9, build 2299929.1031.3939.1156.0559.9663.41
Windows64, Prime95, v28.10, build 1299926.5228.6936.0744.9658.6160.83
Windows64, Prime95, v29.3, build 12999
Windows64, Prime95, v29.3, build 12999
Windows64, Prime95, v29.4, build 72999
Windows64, Prime95, v28.10, build 1299976.2778.54126.10127.93172.65186.55
Windows64, Prime95, v30.3, build 62999
Linux64, Prime95, v30.3, build 6299929.7737.4746.7056.0561.94
Windows64, Prime95, v28.7, build 1299727.1632.4237.4546.0555.3260.78
Windows64, Prime95, v29.4, build 82997
Windows64, Prime95, v29.4, build 82997
Windows64, Prime95, v28.10, build 1299634.2936.3346.0757.4668.8475.95
Windows64, Prime95, v28.7, build 1299227.3929.3737.2946.1055.9961.36
Windows64, Prime95, v28.9, build 2299231.6632.2842.2352.4863.7474.38
Windows64, Prime95, v28.9, build 2299228.4329.9337.6346.9356.9761.90
Windows64, Prime95, v28.9, build 2299227.0533.4839.5953.4261.0061.18
Windows64, Prime95, v28.9, build 2299232.0937.5644.4755.4067.1172.59
Windows64, Prime95, v28.9, build 2299235.7039.7647.3361.8874.8980.22
Windows64, Prime95, v28.10, build 1299226.8928.8536.4246.0355.4260.56
Windows64, Prime95, v29.1, build 142992
Windows64, Prime95, v28.10, build 1299234.0134.4343.3453.5767.8472.24
Windows64, Prime95, v29.1, build 142992
Windows64, Prime95, v28.10, build 1299231.7333.7042.7061.4864.3370.93
Linux64, Prime95, v28.10, build 1299225.8828.0635.3943.9752.7258.16
Windows64, Prime95, v29.4, build 7299226.6028.5736.3345.0054.4959.36
Windows64, Prime95, v29.4, build 7299226.5828.5536.6945.0954.4859.44
Windows64, Prime95, v29.4, build 7299226.7228.8135.9945.3355.0059.77
Windows64, Prime95, v29.4, build 7299226.5928.5136.4545.3755.0759.36
Windows64, Prime95, v29.4, build 7299226.5428.6036.0445.7354.4259.51
Windows64, Prime95, v29.4, build 7299226.4328.4335.8244.8854.4559.37
Windows64, Prime95, v29.4, build 7299226.9028.9637.9345.2654.9559.84
Windows64, Prime95, v29.4, build 7299226.6728.7237.9545.3654.8059.59
Windows64, Prime95, v29.4, build 7299226.5428.7537.9544.9854.1159.88
Windows64, Prime95, v29.4, build 7299226.6128.8037.9445.4954.9659.84
Windows64, Prime95, v29.4, build 72992
Windows64, Prime95, v29.4, build 82992
Windows64, Prime95, v29.4, build 82992
Windows64, Prime95, v29.4, build 82992
Windows64, Prime95, v29.4, build 82992
Windows64, Prime95, v29.4, build 82992
Windows64, Prime95, v29.4, build 82992
Windows64, Prime95, v29.4, build 82992
Windows64, Prime95, v29.8, build 62992
Windows64, Prime95, v29.8, build 62992
Windows64, Prime95, v28.9, build 2299226.5528.7035.9245.1854.3060.28
Windows64, Prime95, v30.3, build 62992
Windows64, Prime95, v29.6, build 62991
Windows64, Prime95, v30.3, build 62991
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: