Marin Mersenne2^P-1
Forgot password?
Great Internet Mersenne Prime Search
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-3350P CPU @ 3.10GHz
Stock Speed   3100 MHz
Features Prefetch,SSE,SSE2,SSE4,AVX
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.10, build 1310012.9515.1818.4322.1827.4333.05
Windows64, Prime95, v29.4, build 73100
Windows64, Prime95, v29.4, build 73100
Windows64, Prime95, v29.4, build 83100
Windows64, Prime95, v28.10, build 1307017.3821.9926.8530.7338.5345.79
Windows64, Prime95, v28.10, build 1306313.8215.9219.5223.0328.7034.73
Windows64, Prime95, v28.10, build 1306313.9917.0520.1524.7530.9737.67
Windows64, Prime95, v28.10, build 1306314.0015.7319.5323.8331.7136.23
Windows64, Prime95, v28.5, build 2305527.6630.1641.2846.9563.4946.24
Windows64, Prime95, v28.7, build 1305512.8114.4918.8622.6426.9330.33
Windows64, Prime95, v28.9, build 2305514.3116.9020.6425.6331.5037.92
Windows64, Prime95, v28.7, build 1305513.6915.0018.9622.7029.2331.67
Windows64, Prime95, v28.7, build 1305512.6816.1918.4024.0527.7330.39
Windows64, Prime95, v28.7, build 1305513.1714.7818.6722.8728.0631.40
Windows64, Prime95, v28.7, build 1305513.5615.1119.4823.5728.8332.04
Windows64, Prime95, v28.9, build 2305513.2416.3518.6624.5431.3133.85
Windows64, Prime95, v28.7, build 1305412.8414.1518.1322.0026.9030.38
Windows64, Prime95, v28.7, build 1295713.7816.1918.8024.2329.4831.48
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: