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) i5 CPU 760 @ 2.80GHz
Stock Speed   2800 MHz
Features Prefetch,SSE,SSE2,SSE4
L1 Cache 32 KB
L2 Cache 256 KB
L3 Cache 8192 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.5, build 2294027.1230.7439.0248.0156.9564.37
Windows64, Prime95, v27.9, build 1293327.6031.2340.4649.6258.9766.095.07
Windows64, Prime95, v28.4, build 1293327.5931.5539.8449.2558.2265.544.78
Windows64, Prime95, v28.5, build 1293331.8041.9650.0462.4959.7974.78
Windows64, Prime95, v28.6, build 1293330.4036.0843.9455.4077.3379.62
Windows64, Prime95, v28.9, build 2293330.2936.3744.9053.6763.4072.98
Windows64, Prime95, v28.9, build 2293329.1832.8741.6851.3561.2171.33
Windows64, Prime95, v28.10, build 1293342.8646.6960.5884.3286.5295.93
Windows64, Prime95, v28.9, build 2293327.3230.8038.9447.9556.8964.39
Windows64, Prime95, v28.9, build 2293330.8130.9339.4049.0465.4672.92
Windows64, Prime95, v28.5, build 2293129.4933.0440.8658.5862.4068.92
Windows64, Prime95, v28.5, build 2293127.4630.8438.8647.9156.9164.14
Windows64, Prime95, v28.9, build 2293133.4838.3248.4958.2973.1077.01
Mac OS X 64-bit, Prime95, v28.9, build 2293151.3061.1377.2890.86105.26193.59
Windows64, Prime95, v28.7, build 1292626.9830.4338.6247.2557.7463.28
Mac OS X 64-bit, Prime95, v28.9, build 2292527.3131.1538.7847.8256.7864.37
Windows64, Prime95, v28.9, build 2279648.9553.46117.30123.2298.47116.54
Windows64, Prime95, v28.10, build 1279332.1840.2487.4793.2880.9180.90
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: