Notebookcheck Logo

Intel Core i5-8279U vs Intel Core i5-8259U vs Intel Core i7-8557U

Intel Core i5-8279U

► remove from comparison

The Intel Core i5-8279U is a quad-core SoC for notebooks based on the Coffee Lake architecture and was announced in the first quarter of 2019. Compared to its predecessor Core i5-7287U, the CPU is now a quad-core with Hyperthreading support for the execution of up to 8 threads simultaneously. The base frequency is 2.4 GHz, but the Turbo goes all the way up to 4.1 GHz. It is also equipped with an Intel Iris Plus Graphics 655 GPU with 128 MB eDRAM, a dual-channel memory controller (DDR4) as well as VP9 and H.265 video decoding as well as encoding. The chip is still manufactured in a 14nm process with FinFET transistors. 

Compared to faster Core i7 model (e.g. Core i7-8559U) with eDRAM and 28 Watts, the i5-8279U only features 6 MB smart cache and a slower clock of the Iris Plus GPU.

Architecture

Intel basically uses the same micro architecture compared to Kaby Lake, so the per-MHz performance does not differ. The manufacturer only reworked the Speed Shift technology for faster dynamic adjustments of voltages and clocks, and the improved 14nm process allows much higher frequencies combined with better efficiency than before.

Performance

Considering the clocks of the Core i5-8259U, its performance should be between above the 15W model Core i7-8650U. The i5-82769U should still be faster than the i7-8650U in practice thanks to the increased TDP, especially during sustained workloads. Compared to the similar named Intel Core i5-8269U, the 8279U offers a slightly lower performance (-200 MHz Turbo, -100 MHz base) although the name suggests otherwise.

Graphics

The integrated Intel Iris Plus 655 Graphics is the GT3e model of the Kaby Lake GPU (Intel Gen. 9.5). It has 48 Execution Units running at 300-1150 MHz and the performance is comparable to a GeForce 930M or 940MX thanks to fast eDRAM cache. However, there aren't any significant improvements compared to the old Iris Plus 650, so modern games can often not be played smoothly or only at the lowest or medium settings, respectively.

Contrary to Skylake, Kaby lake now also supports H.265/HEVC Main 10 with a 10-bit color depth as well as Google's VP9 codec. The dual-core Kaby Lake processors announced in January should also support HDCP 2.2.

Power Consumption

The chip is manufactured in an improved 14nm process with FinFET transistors, which improves the efficiency even further. Intel specifies the TDP with 28 Watts, which can be reduced to 23 Watts (cTDP Down) depending on the usage scenario. The TDP is pretty high compared to the common 15-Watt TDP for quad-core processors, but allows a better utilization of CPU and GPU Turbo.

Intel Core i5-8259U

► remove from comparison

The Intel Core i5-8259U is a quad-core SoC for notebooks based on the Coffee Lake architecture and was announced in April 2018. Compared to its predecessor Core i5-7267U, the CPU is now a quad-core with Hyperthreading support for the execution of up to 8 threads simultaneously. The base frequency is 2.3 GHz, but the Turbo goes all the way up to 3.8 GHz. It is also equipped with an Intel Iris Plus Graphics 655 GPU with 128 MB eDRAM, a dual-channel memory controller (DDR4) as well as VP9 and H.265 video decoding as well as encoding. The chip is still manufactured in a 14nm process with FinFET transistors.

Compared to faster Core i5 and i7 models with eDRAM and 28 Watts, the i5-8259U only features 6 MB smart cache and the slowest clock of the Iris Plus GPU.

Architecture

Intel basically uses the same micro architecture compared to Kaby Lake, so the per-MHz performance does not differ. The manufacturer only reworked the Speed Shift technology for faster dynamic adjustments of voltages and clocks, and the improved 14nm process allows much higher frequencies combined with better efficiency than before.

Performance

Considering the clocks of the Core i5-8259U, its performance should be between the 15W models Core i5-8350U and Core i7-8550U. The i5-8259U should still be faster than the i7-8550U in practice thanks to the increased TDP, especially during sustained workloads.

Graphics

The integrated Intel Iris Plus 655 Graphics is the GT3e model of the Kaby Lake GPU (Intel Gen. 9.5). It has 48 Execution Units running at 300-1050 MHz (slowest clock of the 655, the fastest is 1200 MHz in combination with the i7-8559U) and the performance is comparable to a GeForce 930M or 940MX thanks to fast eDRAM cache. However, there aren't any significant improvements compared to the old Iris Plus 650, so modern games can often not be played smoothly or only at the lowest or medium settings, respectively.

Contrary to Skylake, Kaby lake now also supports H.265/HEVC Main 10 with a 10-bit color depth as well as Google's VP9 codec. The dual-core Kaby Lake processors announced in January should also support HDCP 2.2.

Power Consumption

The chip is manufactured in an improved 14nm process with FinFET transistors, which improves the efficiency even further. Intel specifies the TDP with 28 Watts, which can be reduced to 23 Watts (cTDP Down) depending on the usage scenario. The TDP is pretty high compared to the common 15-Watt TDP for quad-core processors, but allows a better utilization of CPU and GPU Turbo.

Intel Core i7-8557U

► remove from comparison

The Intel Core i7-8557U is a quad-core SoC for notebooks based on the Coffee Lake architecture that was announced in the new entry level MacBook Pro 13 in mid 2019. Compared to its predecessor, the CPU is now a quad-core with Hyperthreading support for the execution of up to 8 threads simultaneously. The base frequency is only 1.7 GHz, but the Turbo goes all the way up to 4.5 GHz. It is also equipped with an Intel Iris Plus Graphics 645 GPU with 128 MB eDRAM, a dual-channel memory controller (DDR4) as well as VP9 and H.265 video decoding as well as encoding. The chip is still manufactured in a 14nm process with FinFET transistors.

Compared to slower Core i5 model with eDRAM and 15 Watts, the i5-8557U features 8 MB smart cache and the fastest clock of the Iris Plus GPU.

Architecture

Intel basically uses the same micro architecture compared to Kaby Lake, so the per-MHz performance does not differ. The manufacturer only reworked the Speed Shift technology for faster dynamic adjustments of voltages and clocks, and the improved 14nm process allows much higher frequencies combined with better efficiency than before.

Performance

Clocked at up to 4.5 GHz, the Core i7-8557U should offer an excellent single thread performance. The multi core performance is greatly improved due to the two additional cores (compared to the predecessor) but may be limited by the 15 Watt TDP (especially for sustained workloads).

Graphics

The integrated Intel Iris Plus 645 Graphics is the GT3e model of the Coffee Lake GPU (Intel Gen. 9.5). It has 48 Execution Units running at 300-1150 MHz  and the performance is comparable to a GeForce 930M or 940MX thanks to fast eDRAM cache. However, there aren't any significant improvements compared to the old Iris Plus 650, so modern games can often not be played smoothly or only at the lowest or medium settings, respectively.

Contrary to Skylake, Kaby lake now also supports H.265/HEVC Main 10 with a 10-bit color depth as well as Google's VP9 codec. The dual-core Kaby Lake processors announced in January should also support HDCP 2.2.

Power Consumption

The chip is manufactured in an improved 14nm++ process with FinFET transistors, which improves the efficiency even further. Intel specifies the TDP with 15 Watts and therefore suited for thin and light laptops.

ModelIntel Core i5-8279UIntel Core i5-8259UIntel Core i7-8557U
SeriesIntel Coffee LakeIntel Coffee LakeIntel Coffee Lake
CodenameCoffee Lake-UCoffee Lake-UCoffee Lake-U
Series: Coffee Lake Coffee Lake-U
Intel Core i7-8559U2.7 - 4.5 GHz4 / 88 MB
Intel Core i7-8557U1.7 - 4.5 GHz4 / 88 MB
Intel Core i5-8269U2.6 - 4.2 GHz4 / 86 MB
» Intel Core i5-8279U2.4 - 4.1 GHz4 / 86 MB
Intel Core i5-8259U2.3 - 3.8 GHz4 / 86 MB
Intel Core i5-8257U1.4 - 3.9 GHz4 / 86 MB
Intel Core i3-8109U3 - 3.6 GHz2 / 44 MB
Intel Core i7-8559U2.7 - 4.5 GHz4 / 88 MB
Intel Core i7-8557U1.7 - 4.5 GHz4 / 88 MB
Intel Core i5-8269U2.6 - 4.2 GHz4 / 86 MB
Intel Core i5-8279U2.4 - 4.1 GHz4 / 86 MB
» Intel Core i5-8259U2.3 - 3.8 GHz4 / 86 MB
Intel Core i5-8257U1.4 - 3.9 GHz4 / 86 MB
Intel Core i3-8109U3 - 3.6 GHz2 / 44 MB
Intel Core i7-8559U2.7 - 4.5 GHz4 / 88 MB
» Intel Core i7-8557U1.7 - 4.5 GHz4 / 88 MB
Intel Core i5-8269U2.6 - 4.2 GHz4 / 86 MB
Intel Core i5-8279U2.4 - 4.1 GHz4 / 86 MB
Intel Core i5-8259U2.3 - 3.8 GHz4 / 86 MB
Intel Core i5-8257U1.4 - 3.9 GHz4 / 86 MB
Intel Core i3-8109U3 - 3.6 GHz2 / 44 MB
Clock2400 - 4100 MHz2300 - 3800 MHz1700 - 4500 MHz
L1 Cache256 KB256 KB256 KB
L2 Cache1 MB1 MB1 MB
L3 Cache6 MB6 MB8 MB
Cores / Threads4 / 84 / 84 / 8
TDP28 Watt28 Watt28 Watt
Technology14 nm14 nm14 nm
max. Temp.100 °C100 °C100 °C
SocketFCBGA1528FCBGA1528FCBGA1528
FeaturesDual-Channel DDR4 Memory Controller, HyperThreading, AVX, AVX2, Quick Sync, Virtualization, AES-NI, Intel SSE4.1, Intel SSE 4.2Dual-Channel DDR4 Memory Controller, HyperThreading, AVX, AVX2, Quick Sync, Virtualization, AES-NI, Intel SSE4.1, Intel SSE 4.2Dual-Channel DDR4 Memory Controller, HyperThreading, AVX, AVX2, Quick Sync, Virtualization, AES-NI, Intel SSE4.1, Intel SSE 4.2
iGPUIntel Iris Plus Graphics 655 (300 - 1150 MHz)Intel Iris Plus Graphics 655 (300 - 1050 MHz)Intel Iris Plus Graphics 645 (300 - 1150 MHz)
Architecturex86x86x86
Announced
ManufacturerIntel Coffee Lake i5-8279UIntel Coffee Lake i5-8259UIntel Coffee Lake i7-8557U

Benchmarks

Performance Rating - CB R15 + R20 + 7-Zip + X265 + Blender + 3DM11 CPU - i5-8259U
35.8 pt (42%)
Cinebench R23 - Cinebench R23 Multi Core
min: 3592     avg: 3734     median: 3714 (6%)     max: 3917 Points
Cinebench R23 - Cinebench R23 Single Core
min: 973     avg: 981     median: 980 (49%)     max: 991 Points
Cinebench R20 - Cinebench R20 CPU (Single Core)
421 Points (54%)
min: 369     avg: 379.5     median: 381.5 (49%)     max: 386 Points
Cinebench R20 - Cinebench R20 CPU (Multi Core)
1717 Points (7%)
min: 1385     avg: 1450     median: 1451.5 (6%)     max: 1512 Points
Cinebench R15 - Cinebench R15 CPU Multi 64 Bit
min: 743     avg: 750     median: 750 (8%)     max: 757 Points
04080120160200240280320360400440480520560600640680720Tooltip
min: 575     avg: 620     median: 611.5 (6%)     max: 687 Points
03570105140175210245280315350385420455490525560595630665Tooltip
Cinebench R15 - Cinebench R15 CPU Single 64 Bit
min: 166     avg: 167.5     median: 167.5 (57%)     max: 169 Points
min: 132     avg: 147.3     median: 151 (52%)     max: 154 Points
Cinebench R11.5 - Cinebench R11.5 CPU Multi 64 Bit
8.3 Points (15%)
Cinebench R11.5 - Cinebench R11.5 CPU Single 64 Bit
1.9 Points (55%)
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
6551 Points (59%)
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
24096 Points (33%)
wPrime 2.10 - wPrime 2.0 1024m *
266.1 s (3%)
wPrime 2.10 - wPrime 2.0 32m *
8.6 s (2%)
WinRAR - WinRAR 4.0
5862 Points (34%)
7-Zip 18.03 - 7-Zip 18.03 Multli Thread 4 runs
22683 MIPS (16%)
min: 17799     avg: 21188     median: 19407 (14%)     max: 28824 MIPS
7-Zip 18.03 - 7-Zip 18.03 Single Thread 4 runs
4276 MIPS (61%)
min: 3951     avg: 3988     median: 3981 (57%)     max: 4022 MIPS
X264 HD Benchmark 4.0 - x264 Pass 2
45.7 fps (21%)
38.5 fps (17%)
X264 HD Benchmark 4.0 - x264 Pass 1
190 fps (52%)
162.3 fps (44%)
HWBOT x265 Benchmark v2.2 - HWBOT x265 4k Preset
6 fps (13%)
012345678910111213Tooltip
min: 4.72     avg: 5.1     median: 5.4 (11%)     max: 5.42 fps
0123456789101112Tooltip
Blender - Blender 2.79 BMW27 CPU *
627 Seconds (4%)
min: 699     avg: 739     median: 755 (5%)     max: 769 Seconds
R Benchmark 2.5 - R Benchmark 2.5 *
min: 0.738     avg: 0.8     median: 0.8 (17%)     max: 0.806 sec
3DMark 06 - CPU - 3DMark 06 - CPU
8830 Points (19%)
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
9.2 s (2%)
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
21.3 s (1%)
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
512 s (2%)
3DMark 11 - 3DM11 Performance Physics
min: 7105     avg: 8284     median: 8391 (29%)     max: 9276 Points
3DMark - 3DMark Ice Storm Physics
21476 Points (14%)
47878 Points (31%)
3DMark - 3DMark Ice Storm Extreme Physics
21581 Points (18%)
47855 Points (40%)
3DMark - 3DMark Ice Storm Unlimited Physics
24185 Points (20%)
min: 17718     avg: 33720     median: 33720 (28%)     max: 49722 Points
3DMark - 3DMark Cloud Gate Physics
7017 Points (18%)
min: 5946     avg: 6710     median: 6654 (17%)     max: 7927 Points
3DMark - 3DMark Fire Strike Standard Physics
10411 Points (26%)
min: 8348     avg: 9499     median: 8871 (22%)     max: 11006 Points
3DMark - 3DMark Time Spy CPU
3439 Points (18%)
min: 2752     avg: 3045     median: 3042 (16%)     max: 3302 Points
Geekbench 4.1 - 4.4 - Geekbench 4.1 - 4.4 64 Bit Single-Core
4850 Points (56%)
min: 4200     avg: 4292     median: 4291.5 (50%)     max: 4383 Points
Geekbench 4.1 - 4.4 - Geekbench 4.1 - 4.4 64 Bit Multi-Core
17643 Points (22%)
min: 13421     avg: 13691     median: 13691 (17%)     max: 13961 Points
Geekbench 5.0 - Geekbench 5.0 64 Bit Single-Core
min: 948     avg: 964     median: 963.5 (49%)     max: 979 Points
Geekbench 5.0 - Geekbench 5.0 64 Bit Multi-Core
min: 3335     avg: 3451     median: 3451 (11%)     max: 3567 Points
Geekbench 5.3 - Geekbench 5.1 - 5.4 64 Bit Single-Core
min: 951     avg: 968     median: 967.5 (47%)     max: 984 Points
1079 Points (53%)
Geekbench 5.3 - Geekbench 5.1 - 5.4 64 Bit Multi-Core
min: 3359     avg: 3483     median: 3483 (12%)     max: 3607 Points
4119 Points (14%)
Mozilla Kraken 1.1 - Kraken 1.1 Total Score *
740 ms (1%)
min: 1010     avg: 1046     median: 1039.5 (1%)     max: 1095 ms
Octane V2 - Octane V2 Total Score
44259 Points (46%)
WebXPRT 3 - WebXPRT 3 Score
min: 173.3     avg: 175.6     median: 176 (48%)     max: 177 Points
Power Consumption - Prime95 Power Consumption - external Monitor *
min: 36.1     avg: 43.2     median: 43.2 (7%)     max: 50.3 Watt
051015202530354045505560Tooltip
Power Consumption - Cinebench R15 Multi Power Consumption - external Monitor *
min: 37.6     avg: 44.5     median: 44.5 (12%)     max: 51.3 Watt
051015202530354045505560Tooltip
Power Consumption - Cinebench R15 Multi Power Efficiency - external Monitor
min: 12.4     avg: 13.9     median: 13.9 (16%)     max: 15.3 Points per Watt

Average Benchmarks Intel Core i5-8279U → NAN% n=

Average Benchmarks Intel Core i5-8259U → NAN% n=

Average Benchmarks Intel Core i7-8557U → NAN% n=

- 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

v1.17
log 25. 00:56:36

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

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

#2 checking url part for id 11435 +0s ... 0s

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

#4 did not recreate cache, as it is less than 5 days old! Created at Wed, 22 Jun 2022 13:12:54 +0200 +0s ... 0s

#5 linkCache_getLink no uid found +0.005s ... 0.005s

#6 linkCache_getLink no uid found +0.002s ... 0.007s

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

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

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

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

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

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

#13 linkCache_getLink no uid found +0.001s ... 0.008s

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

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

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

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

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

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

#20 composed specs +0s ... 0.008s

#21 did output specs +0s ... 0.008s

#22 getting avg benchmarks for device 11503 +0s ... 0.009s

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

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

#25 got single benchmarks 11503 +0.006s ... 0.015s

#26 linkCache_getLink using $NBC_LINKCACHE +0.003s ... 0.018s

#27 getting avg benchmarks for device 10068 +0.001s ... 0.019s

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

#29 got single benchmarks 10068 +0.01s ... 0.03s

#30 getting avg benchmarks for device 11435 +0s ... 0.03s

#31 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.031s

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

#33 got single benchmarks 11435 +0.004s ... 0.035s

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

#35 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.036s

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

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

#38 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.037s

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

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

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

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

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

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

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

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

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

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

#49 linkCache_getLink using $NBC_LINKCACHE +0.007s ... 0.044s

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

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

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

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

#54 linkCache_getLink using $NBC_LINKCACHE +0.034s ... 0.078s

#55 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.078s

#56 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.078s

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

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

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

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

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

#62 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.079s

#63 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.079s

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

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

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

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

#68 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.081s

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

#70 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.082s

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

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

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

#74 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.082s

#75 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.082s

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

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

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

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

#80 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.083s

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

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

#83 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.084s

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

#85 linkCache_getLink using $NBC_LINKCACHE +0.011s ... 0.095s

#86 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.095s

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

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

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

#90 linkCache_getLink using $NBC_LINKCACHE +0.029s ... 0.123s

#91 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.124s

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

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

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

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

#96 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.124s

#97 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.124s

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

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

#100 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.125s

#101 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.126s

#102 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.126s

#103 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.127s

#104 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.127s

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

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

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

#108 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.127s

#109 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.128s

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

#111 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.129s

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

#113 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.13s

#114 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.13s

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

#116 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.131s

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

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

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

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

#121 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.131s

#122 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.132s

#123 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.132s

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

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

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

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

#128 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.133s

#129 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.133s

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

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

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

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

#134 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.134s

#135 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.134s

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

#137 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.135s

#138 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.135s

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

#140 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.136s

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

#142 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.137s

#143 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.137s

#144 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.137s

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

#146 linkCache_getLink no uid found +0s ... 0.138s

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

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

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

#150 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.139s

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

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

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

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

#155 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.14s

#156 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.14s

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

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

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

#160 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.141s

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

#162 linkCache_getLink using $NBC_LINKCACHE +0.009s ... 0.15s

#163 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.15s

#164 linkCache_getLink using $NBC_LINKCACHE +0.007s ... 0.156s

#165 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.156s

#166 min, max, avg, median took s +0.001s ... 0.157s

#167 return log +0s ... 0.157s

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)