Notebookcheck Logo

Intel Core i7-3940XM vs Intel Core i7-3667U

Intel Core i7-3940XM

► remove from comparison Intel 3940XM

The Intel Core i7-3940XM is the fastest quad-core processor for laptops (at the time of introduction in September 2012) an successor of the i7-3920XM. Due to Hyperthreading, the four cores can handle up to eight threads in parallel leading to better utilization of the CPU. Each core offers a base speed of 3.0 GHz but can dynamically increase clock rates with Turbo Boost up to 3.7 GHz (for 4 active cores), 3.8 GHz (for 2 active cores) and 3.9 GHz (for 1 active core). Furthermore, the Extreme CPUs offer an unlocked multiplicator for easy overclocking.

Ivy Bridge is an enhanced die shrink of the Sandy Bridge architecture with improvements on both GPU and CPU performance. The CPUs are produced in 22nm (versus 32nm Sandy Bridge CPUs) and are the first to introduce 3D transistors for increased energy efficiency when compared to similarly clocked Sandy Bridge processors. Other new features are integrated PCI Express 3.0 and  DDR3(L)-1600 support.

The performance of the Core i7-3940XM should be slightly above a similarly clocked Sandy Bridge processor due to slight architectural improvements. Because of the higher clock speed, the former champion Core i7-3920XM should be outperformed by about 3%.

The integrated Intel HD Graphics 4000 offers 16 Execution Units (EUs) clocked at 650 MHz up to 1350 MHz with Turbo Boost, making it the fastest variant.

The XM CPUs are rated at a TDP of 55 Watts including graphics card and memory controller and therefore 10 Watt higher than the other quad-core models.  Therefore, the CPU is well-suited for laptops 17-inches or greater.

Intel Core i7-3667U

► remove from comparison

The Intel Core i7-3667U is the fastest ULV-processor for laptops based on the Ivy Bridge architecture at the time of introduction in Q2 2012. Due to Hyperthreading, the two cores can handle up to four threads in parallel leading to better utilization of the CPU. Each core offers a base speed of 2.0 GHz but can dynamically increase clock rates with Turbo Boost up to 3.0 GHz (for 2 active cores) and 3.2 GHz (for 1 active core). As its Sandy-Bridge-based predecessors, it offers a 4 MB L3-Cache.

Ivy Bridge is an enhanced die shrink of the Sandy Bridge architecture with improvements on both GPU and CPU performance. The CPUs are produced in 22nm (versus 32nm Sandy Bridge CPUs) and are the first to introduce 3D transistors for increased energy efficiency when compared to similarly clocked Sandy Bridge processors. Other new features are integrated PCI Express 3.0 and  DDR3(L)-1600 support.

The performance of the Core i7-3667U is slightly above a similarly clocked Sandy Bridge processor due to the architectural improvements. Therefore, and because of the higher clock speed, the Core i7-2677M is easily outperformed by 10 to 15%.

The integrated Intel HD Graphics 4000 offers 16 Execution Units (EUs) clocked at 350 MHz up to 1150 MHz with Turbo Boost, delivering a performance comparable with an AMD Radeon HD 6620G.

The ULV-CPUs are rated at a TDP of 17 W including graphics card and memory controller.  Therefore, the CPU is suited for small laptops and ultrabooks.

ModelIntel Core i7-3940XMIntel Core i7-3667U
SeriesIntel Core i7Intel Core i7
CodenameIvy BridgeIvy Bridge
Series: Core i7 Ivy Bridge
» Intel Core i7-3940XM3 - 3.9 GHz4 / 88 MB
Intel Core i7-3920XM compare2.9 - 3.8 GHz4 / 88 MB
Intel Core i7-3840QM compare2.8 - 3.8 GHz4 / 88 MB
Intel Core i7-3820QM compare2.7 - 3.7 GHz4 / 88 MB
Intel Core i7-3740QM compare2.7 - 3.7 GHz4 / 86 MB
Intel Core i7-3720QM compare2.6 - 3.6 GHz4 / 86 MB
Intel Core i7-3635QM compare2.4 - 3.4 GHz4 / 86 MB
Intel Core i7-3630QM compare2.4 - 3.4 GHz4 / 86 MB
Intel Core i7-3615QM compare2.3 - 3.3 GHz4 / 86 MB
Intel Core i7-3610QM compare2.3 - 3.3 GHz4 / 86 MB
Intel Core i7-3632QM compare2.2 - 3.2 GHz4 / 86 MB
Intel Core i7-3612QM compare2.1 - 3.1 GHz4 / 86 MB
Intel Core i7-3540M compare3 - 3.7 GHz2 / 44 MB
Intel Core i7-3520M compare2.9 - 3.6 GHz2 / 44 MB
Intel Core i7-3687U compare2.1 - 3.3 GHz2 / 44 MB
Intel Core i7-3667U2 - 3.2 GHz2 / 44 MB
Intel Core i7-3537U compare2 - 3.1 GHz2 / 44 MB
Intel Core i7-3517U compare1.9 - 3 GHz2 / 44 MB
Intel Core i7-3689Y compare1.5 - 2.6 GHz2 / 44 MB
Intel Core i7-3940XM3 - 3.9 GHz4 / 88 MB
Intel Core i7-3920XM compare2.9 - 3.8 GHz4 / 88 MB
Intel Core i7-3840QM compare2.8 - 3.8 GHz4 / 88 MB
Intel Core i7-3820QM compare2.7 - 3.7 GHz4 / 88 MB
Intel Core i7-3740QM compare2.7 - 3.7 GHz4 / 86 MB
Intel Core i7-3720QM compare2.6 - 3.6 GHz4 / 86 MB
Intel Core i7-3635QM compare2.4 - 3.4 GHz4 / 86 MB
Intel Core i7-3630QM compare2.4 - 3.4 GHz4 / 86 MB
Intel Core i7-3615QM compare2.3 - 3.3 GHz4 / 86 MB
Intel Core i7-3610QM compare2.3 - 3.3 GHz4 / 86 MB
Intel Core i7-3632QM compare2.2 - 3.2 GHz4 / 86 MB
Intel Core i7-3612QM compare2.1 - 3.1 GHz4 / 86 MB
Intel Core i7-3540M compare3 - 3.7 GHz2 / 44 MB
Intel Core i7-3520M compare2.9 - 3.6 GHz2 / 44 MB
Intel Core i7-3687U compare2.1 - 3.3 GHz2 / 44 MB
» Intel Core i7-3667U2 - 3.2 GHz2 / 44 MB
Intel Core i7-3537U compare2 - 3.1 GHz2 / 44 MB
Intel Core i7-3517U compare1.9 - 3 GHz2 / 44 MB
Intel Core i7-3689Y compare1.5 - 2.6 GHz2 / 44 MB
Clock3000 - 3900 MHz2000 - 3200 MHz
L1 Cache256 KB128 KB
L2 Cache1 MB512 KB
L3 Cache8 MB4 MB
Cores / Threads4 / 82 / 4
TDP55 Watt17 Watt
Transistors1400 Million
Technology22 nm22 nm
Die Size160 mm2
max. Temp.105 °C105 °C
SocketFCPGA988BGA1023
FeaturesHD Graphics 4000, DDR3(L)-1600 Memory Controller, HyperThreading, AVX, Quick Sync, VirtualizationTurbo Boost 2.0, Hyper-Threading, Virtualization VT-x, Virtualization for Directed I/O (VT-d), Trusted Execution, AES, Intel 64, Anti-Theft, My WiFi, Idle States, Enhanced SpeedStep, Thermal Monitorin, Execute Disable Bit
iGPUIntel HD Graphics 4000 (650 - 1350 MHz)Intel HD Graphics 4000 (350 - 1150 MHz)
Architecturex86x86
$1096 U.S.$346 U.S.
Announced
ManufacturerIntel Core i7 3667U

Benchmarks

Cinebench R11.5 - Cinebench R11.5 CPU Multi 64 Bit
min: 7.45     avg: 7.5     median: 7.5 (14%)     max: 7.46 Points
min: 2.55     avg: 2.8     median: 2.9 (5%)     max: 2.96 Points
Cinebench R11.5 - Cinebench R11.5 CPU Single 64 Bit
min: 1.62     avg: 1.6     median: 1.6 (46%)     max: 1.63 Points
min: 1.3     avg: 1.3     median: 1.3 (38%)     max: 1.33 Points
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
min: 5246     avg: 5255     median: 5252 (47%)     max: 5267 Points
min: 3975     avg: 4215     median: 4215 (38%)     max: 4455 Points
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
min: 20438     avg: 20582     median: 20564 (28%)     max: 20744 Points
min: 8290     avg: 8810     median: 8809.5 (12%)     max: 9329 Points
Cinebench R10 - Cinebench R10 Rend. Multi (64bit)
min: 25475     avg: 25600     median: 25624 (23%)     max: 25700 Points
min: 10253     avg: 11057     median: 11294.5 (10%)     max: 11387 Points
Cinebench R10 - Cinebench R10 Rend. Single (64bit)
min: 6506     avg: 6621     median: 6669 (41%)     max: 6687 Points
min: 5363     avg: 5524     median: 5563 (34%)     max: 5607 Points
wPrime 2.10 - wPrime 2.0 1024m *
min: 208.8     avg: 219.2     median: 215.7 (3%)     max: 233 s
min: 529     avg: 591     median: 570 (7%)     max: 675 s
wPrime 2.10 - wPrime 2.0 32m *
min: 6.8     avg: 7     median: 7 (1%)     max: 7.169 s
min: 16.27     avg: 17.4     median: 17.8 (4%)     max: 18.1 s
WinRAR - WinRAR 4.0
min: 3467     avg: 4124     median: 4123.5 (24%)     max: 4780 Points
min: 2413     avg: 2474     median: 2474 (14%)     max: 2535 Points
X264 HD Benchmark 4.0 - x264 Pass 2
40.6 fps (18%)
min: 14.54     avg: 15.4     median: 15.4 (7%)     max: 16.32 fps
X264 HD Benchmark 4.0 - x264 Pass 1
161.1 fps (44%)
min: 86.3     avg: 87     median: 87 (24%)     max: 87.7 fps
TrueCrypt - TrueCrypt Serpent
min: 0.373     avg: 0.4     median: 0.4 (13%)     max: 0.386 GB/s
TrueCrypt - TrueCrypt Twofish
min: 0.64     avg: 0.7     median: 0.7 (14%)     max: 0.66 GB/s
min: 0.259     avg: 0.3     median: 0.3 (6%)     max: 0.265 GB/s
TrueCrypt - TrueCrypt AES
min: 3.5     avg: 3.6     median: 3.7 (14%)     max: 3.7 GB/s
min: 1.4     avg: 1.5     median: 1.5 (6%)     max: 1.5 GB/s
3DMark 06 - CPU - 3DMark 06 - CPU
min: 7166     avg: 7182     median: 7176 (15%)     max: 7203 Points
min: 3393     avg: 3567     median: 3594.5 (8%)     max: 3685 Points
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
min: 9     avg: 9.2     median: 9 (2%)     max: 9.554 s
min: 11     avg: 11.5     median: 11.4 (2%)     max: 12 s
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
min: 21     avg: 21.1     median: 21 (1%)     max: 21.26 s
min: 27     avg: 27.4     median: 27.2 (1%)     max: 28 s
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
min: 518     avg: 526     median: 525.5 (2%)     max: 533 s
min: 640     avg: 648     median: 647.5 (3%)     max: 655 s
SiSoft Sandra Dhrystone (MIPS) - SiSoft Sandra Dhrystone (MIPS)
min: 147240     avg: 147620     median: 147620 (70%)     max: 148000 MIPS
52000 MIPS (25%)
SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)
min: 89600     avg: 89630     median: 89630 (69%)     max: 89660 MFLOPS
36570 MFLOPS (28%)
Windows 7 Experience Index - Win7 CPU
7.7 Points (99%)
7.1 Points (91%)
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
min: 25344     avg: 25795     median: 25885 (26%)     max: 26157 Points
min: 8295     avg: 9039     median: 9222 (9%)     max: 9600 Points
3DMark 11 - 3DM11 Performance Physics
min: 7611     avg: 8737     median: 9032 (31%)     max: 9568 Points
min: 2618     avg: 3129     median: 3231 (11%)     max: 3436 Points
3DMark - 3DMark Ice Storm Physics
100%
1 3940XM +
48410 Points (31%)
3DMark - 3DMark Cloud Gate Physics
100%
1 3940XM +
7208 Points (18%)
3DMark - 3DMark Fire Strike Standard Physics
100%
1 3940XM +
9863 Points (24%)
Sunspider - Sunspider 0.9.1 Total Score *
100%
1 3667U +
128 ms (1%)

Average Benchmarks Intel Core i7-3940XM → 100% n=23

Average Benchmarks Intel Core i7-3667U → 62% n=23

- Range of benchmark values for this graphics card
- Average benchmark values for this graphics card
* Smaller numbers mean a higher performance
1 This benchmark is not used for the average calculation

Add one or more devices and compare

In the following list you can select (and also search for) devices that should be added to the comparison. You can select more than one device.

restrict list:

show all (including archived), 2022, 2021
v1.17
log 04. 04:48:04

#0 checking url part for id 3345 +0s ... 0s

#1 checking url part for id 3078 +0s ... 0s

#2 not redirecting to Ajax server +0s ... 0s

#3 did not recreate cache, as it is less than 5 days old! Created at Sat, 02 Jul 2022 13:13:02 +0200 +0s ... 0s

#4 linkCache_getLink using $NBC_LINKCACHE +0.008s ... 0.008s

#5 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.01s

#6 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#7 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#8 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#9 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#10 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#11 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#12 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#13 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#14 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#15 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#16 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#17 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#18 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#19 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#20 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#21 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#22 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#23 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#24 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#25 composed specs +0s ... 0.01s

#26 did output specs +0s ... 0.01s

#27 getting avg benchmarks for device 3345 +0s ... 0.011s

#28 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.011s

#29 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.011s

#30 got single benchmarks 3345 +0.009s ... 0.02s

#31 getting avg benchmarks for device 3078 +0s ... 0.021s

#32 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.021s

#33 got single benchmarks 3078 +0.01s ... 0.031s

#34 got avg benchmarks for devices +0s ... 0.031s

#35 linkCache_getLink no uid found +0s ... 0.032s

#36 linkCache_getLink no uid found +0s ... 0.032s

#37 linkCache_getLink no uid found +0.001s ... 0.033s

#38 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.033s

#39 linkCache_getLink no uid found +0s ... 0.033s

#40 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.033s

#41 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.033s

#42 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.033s

#43 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.033s

#44 linkCache_getLink no uid found +0s ... 0.033s

#45 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.033s

#46 linkCache_getLink no uid found +0s ... 0.033s

#47 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.034s

#48 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.034s

#49 linkCache_getLink no uid found +0s ... 0.034s

#50 linkCache_getLink no uid found +0s ... 0.034s

#51 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.034s

#52 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.034s

#53 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.034s

#54 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.035s

#55 linkCache_getLink no uid found +0s ... 0.035s

#56 linkCache_getLink no uid found +0s ... 0.035s

#57 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.035s

#58 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.035s

#59 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.035s

#60 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.035s

#61 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.035s

#62 linkCache_getLink no uid found +0s ... 0.035s

#63 linkCache_getLink no uid found +0s ... 0.035s

#64 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.035s

#65 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.035s

#66 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.035s

#67 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.035s

#68 linkCache_getLink no uid found +0s ... 0.036s

#69 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.036s

#70 linkCache_getLink no uid found +0s ... 0.036s

#71 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.036s

#72 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.036s

#73 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.036s

#74 linkCache_getLink no uid found +0s ... 0.036s

#75 linkCache_getLink no uid found +0s ... 0.036s

#76 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.037s

#77 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.037s

#78 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.037s

#79 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.037s

#80 linkCache_getLink no uid found +0s ... 0.037s

#81 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.037s

#82 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.037s

#83 linkCache_getLink no uid found +0s ... 0.037s

#84 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.038s

#85 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.038s

#86 linkCache_getLink no uid found +0s ... 0.038s

#87 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.038s

#88 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.038s

#89 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.039s

#90 linkCache_getLink no uid found +0s ... 0.039s

#91 linkCache_getLink no uid found +0s ... 0.039s

#92 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.039s

#93 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.039s

#94 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.039s

#95 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.039s

#96 linkCache_getLink no uid found +0s ... 0.039s

#97 linkCache_getLink no uid found +0s ... 0.039s

#98 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.039s

#99 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.039s

#100 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.039s

#101 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#102 linkCache_getLink no uid found +0s ... 0.04s

#103 linkCache_getLink no uid found +0s ... 0.04s

#104 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#105 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#106 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#107 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#108 linkCache_getLink no uid found +0s ... 0.04s

#109 linkCache_getLink no uid found +0s ... 0.04s

#110 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.041s

#111 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.041s

#112 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.041s

#113 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.041s

#114 linkCache_getLink no uid found +0s ... 0.041s

#115 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.041s

#116 linkCache_getLink no uid found +0s ... 0.041s

#117 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.041s

#118 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.041s

#119 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.041s

#120 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.041s

#121 linkCache_getLink no uid found +0s ... 0.042s

#122 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.042s

#123 linkCache_getLink no uid found +0s ... 0.042s

#124 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.042s

#125 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.042s

#126 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.042s

#127 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.042s

#128 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.042s

#129 linkCache_getLink no uid found +0s ... 0.042s

#130 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.043s

#131 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.043s

#132 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.043s

#133 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.043s

#134 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.043s

#135 linkCache_getLink no uid found +0s ... 0.043s

#136 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.043s

#137 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.043s

#138 linkCache_getLink no uid found +0s ... 0.043s

#139 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.044s

#140 linkCache_getLink no uid found +0s ... 0.044s

#141 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.044s

#142 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.044s

#143 linkCache_getLink no uid found +0s ... 0.044s

#144 linkCache_getLink no uid found +0s ... 0.044s

#145 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.044s

#146 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.045s

#147 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.045s

#148 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.045s

#149 linkCache_getLink no uid found +0s ... 0.045s

#150 linkCache_getLink no uid found +0s ... 0.045s

#151 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.045s

#152 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.045s

#153 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.045s

#154 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.045s

#155 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.045s

#156 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.046s

#157 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.046s

#158 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.046s

#159 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.047s

#160 min, max, avg, median took s +0s ... 0.047s

#161 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.047s

#162 return log +0.003s ... 0.051s

Please share our article, every link counts!
> Notebook / Laptop Reviews and News > Benchmarks / Tech > Processor Comparison - Head 2 Head
Redaktion, 2017-09- 8 (Update: 2017-09-11)