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-4430 CPU @ 3.00GHz
Stock Speed   no stock speed set
Features Prefetch,SSE,SSE2,SSE4,AVX,AVX2,FMA,
L1 Cache 32 KB
L2 Cache 256 KB
L3 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.3, build 130868.7410.0513.2415.6018.8321.982.86
Windows64, Prime95, v28.10, build 129919.7611.3214.1417.1320.3523.68
Windows64, Prime95, v28.10, build 1298410.2111.4415.0618.2421.6525.48
Windows64, Prime95, v28.10, build 129849.9211.9515.1117.7021.7124.61
Linux64, Prime95, v28.5, build 228849.9711.6214.4617.3720.7523.28
Windows64, Prime95, v28.7, build 127939.6111.0714.3216.9120.3424.18
Windows64, Prime95, v28.7, build 127929.2310.4813.7616.0619.2522.11
Windows64, Prime95, v28.5, build 2279111.2512.8116.6919.6623.2726.24
Windows64, Prime95, v28.4, build 127919.7011.4213.8817.5520.7722.513.06
Windows64, Prime95, v28.7, build 1279111.7914.4315.4518.6227.5333.01
Windows64, Prime95, v28.5, build 227859.9611.4615.7917.4020.6223.55
Windows64, Prime95, v28.7, build 1278511.9713.3118.0020.8723.8629.25
Windows64, Prime95, v28.7, build 127859.5010.5013.5216.2319.1622.35
Windows64, Prime95, v28.7, build 127859.7211.5514.5117.3620.8923.66
Windows64, Prime95, v28.4, build 1278517.0912.2915.1330.1727.0924.143.24
Windows64, Prime95, v28.5, build 227859.5411.8514.4817.1423.6823.81
Windows64, Prime95, v28.5, build 227849.7611.3715.3519.5923.3623.89
Mac OS X 64-bit, Prime95, v28.9, build 2278412.8513.5817.1620.2727.2529.45
Windows64, Prime95, v28.7, build 1278410.0411.7314.6017.5420.8323.89
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: