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) i3-4005U CPU @ 1.70GHz
Stock Speed   1696 MHz
Features Hyperthreaded,Prefetch,SSE,SSE2,SSE4,AVX,AVX2,FMA,
L1 Cache 32 KB
L2 Cache 256 KB
L3 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
Windows64, Prime95, v28.6, build 1169616.9418.7523.9629.1834.8238.90
Windows64, Prime95, v28.7, build 1169641.4449.4248.4863.6071.2385.46
Windows64, Prime95, v28.7, build 1169616.1518.4023.2827.9533.5237.81
Windows64, Prime95, v28.7, build 1169636.7642.0053.4167.9279.8394.06
Windows64, Prime95, v28.7, build 1169616.5319.0824.5928.8134.5239.08
Windows64, Prime95, v28.7, build 1169620.4018.3423.2528.0133.4555.76
Windows64, Prime95, v28.9, build 2169623.6626.1928.8439.4649.4449.71
Windows64, Prime95, v28.9, build 2169619.2219.3025.4543.9963.21135.82
Windows64, Prime95, v28.9, build 2169637.2735.7055.8179.9478.5354.51
Windows64, Prime95, v28.9, build 2169619.5323.3027.7432.5041.4448.37
Windows64, Prime95, v28.10, build 1169624.4619.0324.6629.6535.3245.50
Windows64, Prime95, v28.10, build 1169620.9724.8629.5936.8543.5252.04
Windows64, Prime95, v28.10, build 1169618.4520.9925.8831.5548.0142.94
Windows64, Prime95, v28.10, build 1169617.5019.2725.1432.3035.7741.38
Windows64, Prime95, v28.10, build 1169619.8027.3432.3442.3770.9161.01
Windows64, Prime95, v28.10, build 11696109.84150.27183.16237.51258.20305.31
Windows64, Prime95, v29.3, build 11696
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: