CPU Benchmarks for Lucas-Lehmer/Trial Factor

Great Internet Mersenne Prime Search
GIMPS
Finding World Record Primes Since 1996

PrimeNet CPU Benchmarks

Log in to see your benchmarks	Exclude version 25 benchmarks	Exclude overclocked and underclocked data
Show 32-bit benchmarks	Exclude version 26 benchmarks	Exclude benchmarks flagged by users as suspect
Show 64-bit benchmarks	Exclude version 27 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-3240 CPU @ 3.40GHz
Stock Speed	no stock speed set
Features	Hyperthreaded,Prefetch,SSE,SSE2,SSE4,AVX
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 bits
Windows64, Prime95, v28.5, build 2	3502	11.17	13.16	16.30	19.54	24.08	26.96
Windows64, Prime95, v27.9, build 1	3410	16.41	15.82	20.32	22.01	29.18	30.17	2.88
Windows64, Prime95, v28.5, build 2	3400	13.02	14.42	17.73	22.30	27.23	30.12
Windows64, Prime95, v28.9, build 2	3400	12.56	16.14	17.66	23.79	30.35	34.82
Windows64, Prime95, v28.10, build 1	3393	14.24	16.86	21.78	25.10	29.89	37.35
Windows64, Prime95, v27.9, build 1	3392	12.83	17.41	18.71	24.55	28.91	31.12	2.90
Windows64, Prime95, v28.5, build 2	3392	12.05	13.56	17.29	21.03	25.44	29.25
Windows64, Prime95, v28.5, build 2	3392	12.30	14.39	17.98	21.56	26.48	29.99
Windows64, Prime95, v28.5, build 2	3392	11.88	13.68	17.19	21.03	25.52	28.87
Windows64, Prime95, v28.7, build 1	3392	13.52	15.02	19.07	23.54	28.76	31.68
Windows64, Prime95, v28.10, build 1	3392	11.94	14.23	17.30	20.67	25.64	30.88
Windows64, Prime95, v28.10, build 1	3392	12.48	15.03	18.54	21.97	27.00	32.89
Windows64, Prime95, v28.10, build 1	3392	11.94	14.31	17.28	21.18	25.95	31.68
Windows64, Prime95, v28.10, build 1	3392	14.55	17.47	21.99	26.56	36.48	39.41
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:

Username
Password