Marin Mersenne 2^P-1
Username
Password
Forgot password?
Blue
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 AMD Ryzen 5 2600 Six-Core Processor
Stock Speed   no stock speed set
Features Prefetch,SSE,SSE2,SSE4,AVX,AVX2,FMA
L1 Cache 32 KB
L2 Cache 512 KB
L3 Cache 16384 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 1395130.1132.2940.7350.2757.3563.61
Windows64, Prime95, v28.10, build 1382424.9128.4035.6346.2651.8560.43
Windows64, Prime95, v28.10, build 1378127.8033.7141.8449.6558.6869.77
Windows64, Prime95, v28.7, build 1372328.7934.6735.7643.5450.3356.42
Windows64, Prime95, v28.7, build 1370624.3127.7434.7743.0249.3957.41
Mac OS X 64-bit, Prime95, v28.7, build 13703
Windows64, Prime95, v28.10, build 1365426.1830.0137.2646.2053.6260.98
Windows64, Prime95, v28.7, build 1362633.4133.4442.7151.5762.5169.09
Windows64, Prime95, v28.10, build 1360228.4238.7140.6053.2669.3577.10
Windows64, Prime95, v28.7, build 1356325.9929.6636.4645.5852.6960.55
Windows64, Prime95, v28.10, build 1356326.0430.4437.5845.2655.7164.72
Windows64, Prime95, v28.7, build 1354324.8828.3635.0343.5750.3457.69
Windows64, Prime95, v28.7, build 1351826.3329.9237.1346.0253.6961.21
Windows64, Prime95, v28.7, build 1351811.3712.6616.1219.6523.9727.03
Windows64, Prime95, v28.10, build 1347232.4534.3743.8056.8267.7381.52
Windows64, Prime95, v28.7, build 1346427.0330.1641.0051.9754.0762.23
Windows64, Prime95, v28.7, build 1345628.8034.4342.1452.9560.5769.42
Windows64, Prime95, v28.7, build 1341429.7034.5342.1750.5260.0079.51
Windows64, Prime95, v28.7, build 1339827.5831.4539.1148.6056.2864.79
Windows64, Prime95, v28.10, build 1274526.8230.6837.8746.7574.8362.86
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: