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 Intel(R) Core(TM)2 Duo CPU T8300 @ 2.40GHz
Stock Speed   2400 MHz
Features Prefetch,SSE,SSE2,SSE4
L1 Cache 32 KB
L2 Cache 3072 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
Mac OS X 64-bit, Prime95, v27.9, build 1239433.6336.0945.9765.7880.0876.866.58
Mac OS X 64-bit, Prime95, v27.7, build 2239433.7536.2244.9559.0469.8976.166.57
Mac OS X 64-bit, Prime95, v27.7, build 2239469.6878.0071.72127.40129.66146.056.59
Mac OS X 64-bit, Prime95, v27.7, build 2239434.0935.9745.9557.6171.7976.346.68
Mac OS X 64-bit, Prime95, v27.7, build 2239435.3039.2051.8465.6479.90117.926.61
Windows64, Prime95, v27.7, build 2239436.2240.6248.9960.8678.6282.576.76
Mac OS X 64-bit, Prime95, v27.9, build 1239470.4979.7097.21122.84157.41154.5213.24
Mac OS X 64-bit, Prime95, v27.9, build 1239467.2370.0089.54116.86145.42134.608.05
Mac OS X 64-bit, Prime95, v28.7, build 1239476.2572.4269.7197.05109.08117.80
Windows64, Prime95, v28.10, build 1239437.3941.0948.6365.0390.6091.22
Windows64, Prime95, v27.9, build 1239334.2337.6146.0558.6872.9076.9219.97
Mac OS X 64-bit, Prime95, v27.9, build 1239365.3671.10117.52112.17136.04147.4213.36
Windows64, Prime95, v28.5, build 2239334.9337.7747.3660.2173.7879.34
Mac OS X 64-bit, Prime95, v28.5, build 2239365.5670.6588.53111.45135.55147.13
Mac OS X 64-bit, Prime95, v27.9, build 1239334.4036.6946.2157.4872.5677.296.64
Linux64, Prime95, v28.5, build 2239339.5142.9055.9771.2292.3390.40
Mac OS X 64-bit, Prime95, v27.9, build 1239337.8441.4149.6861.4773.0781.886.59
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: