Marin Mersenne 2^P-1
Username
Password
Forgot password?
Black
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-9100F CPU @ 3.60GHz
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, v30.6, build 13984
Windows64, Prime95, v30.7, build 73983
Windows64, Prime95, v28.10, build 139747.558.2511.2812.8815.9917.71
Windows64, Prime95, v30.3, build 43974
Windows64, Prime95, v30.3, build 43974
Windows64, Prime95, v30.3, build 63974
Windows64, Prime95, v28.10, build 1387515.1010.509.9512.0014.4316.63
Windows64, Prime95, v28.7, build 137545.966.928.8510.4712.9014.05
Windows64, Prime95, v29.8, build 63753
Windows64, Prime95, v28.7, build 137536.867.899.3311.1313.8715.29
Windows64, Prime95, v28.7, build 137537.519.0411.0413.5522.0419.64
Windows64, Prime95, v29.8, build 63753
Windows64, Prime95, v29.8, build 63745
Windows64, Prime95, v29.8, build 63745
Windows64, Prime95, v29.8, build 63745
Windows64, Prime95, v29.8, build 63745
Windows64, Prime95, v30.3, build 43577
Windows64, Prime95, v30.3, build 43577
Windows64, Prime95, v30.3, build 43577
Windows64, Prime95, v30.3, build 43577
Windows64, Prime95, v30.3, build 43576
Windows64, Prime95, v29.8, build 63372
Windows64, Prime95, v29.8, build 63371
Windows64, Prime95, v29.8, build 63371
Windows64, Prime95, v29.8, build 63371
Windows64, Prime95, v29.8, build 63371
Windows64, Prime95, v29.8, build 63370
Windows64, Prime95, v28.9, build 21008.529.6112.3514.7816.9719.36
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: