Notebookcheck Logo

Intel Core i5-8279U vs Intel Core i5-8257U vs Intel Core i3-8109U

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-8257U

► remove from comparison

The Intel Core i5-8257U 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.4 GHz, but the Turbo goes all the way up to 3.9 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 faster Core i7-8557U model with eDRAM and 15 Watts, the i5-8257U 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

Thanks to the relative high Turbo Boost clock, the single thread performance should be very good, but still behind the faster i7 model. The short burst all core performance is clearly better compared to the old dual core predecessors thanks to the additional cores. In sustained workloads, the performance is usually limited by the TDP and cooling. In these workloads the difference to the Core i7 should be also smaller.

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-1050 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.

Intel Core i3-8109U

► remove from comparison

The Intel Core i3-8109U is a dual-core SoC for notebooks based on the Coffee Lake architecture and was announced in April 2018. Compared to its predecessor Core i3-7167U, the CPU now supports Turbo boost with up to 3.6 GHz. Thanks to Hyperthreading the CPU can execute up to 4 threads simultaneously. It is also equipped with an Intel Iris Plus Graphics 655 GPU with 128 MB eDRAM (but with 300 - 1050 MHz it is the slowest Iris Plus), 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 (3rd generation) with FinFET transistors.

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

Thanks to the Turbo Boost, the processor performance should be a bit above the old Core i7-7500U (max. 3.5 GHz, 15 Watt). Therefore the Core i3-8109U should be fine for most applications. Some games however already need four real cores for optimal performance (paired with a dedicated GPU e.g.).

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  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 (14nm++, 3rd generation of 14nm) 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.

ModelIntel Core i5-8279UIntel Core i5-8257UIntel Core i3-8109U
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 MHz1400 - 3900 MHz3000 - 3600 MHz
L1 Cache256 KB256 KB128 KB
L2 Cache1 MB1 MB512 KB
L3 Cache6 MB6 MB4 MB
Cores / Threads4 / 84 / 82 / 4
TDP28 Watt15 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 645 (300 - 1050 MHz)Intel Iris Plus Graphics 655 (300 - 1050 MHz)
Architecturex86x86x86
Announced
ManufacturerIntel Coffee Lake i5-8279UIntel Coffee Lake i5-8257UIntel Coffee Lake i3-8109U

Benchmarks

Performance Rating - CB R15 + R20 + 7-Zip + X265 + Blender + 3DM11 CPU - i5-8257U
36.2 pt (43%)
Performance Rating - CB R15 + R20 + 7-Zip + X265 + Blender + 3DM11 CPU - i3-8109U
30.6 pt (36%)
Cinebench R23 - Cinebench R23 Multi Core
4033 Points (7%)
2004 Points (3%)
Cinebench R23 - Cinebench R23 Single Core
1003 Points (50%)
906 Points (45%)
Cinebench R20 - Cinebench R20 CPU (Single Core)
421 Points (54%)
min: 388     avg: 393     median: 393 (51%)     max: 398 Points
351 Points (45%)
Cinebench R20 - Cinebench R20 CPU (Multi Core)
1717 Points (7%)
min: 1494     avg: 1520     median: 1519.5 (6%)     max: 1545 Points
772 Points (3%)
Cinebench R15 - Cinebench R15 CPU Multi 64 Bit
min: 743     avg: 750     median: 750 (8%)     max: 757 Points
04080120160200240280320360400440480520560600640680720Tooltip
min: 629     avg: 634     median: 633.5 (7%)     max: 638 Points
03570105140175210245280315350385420455490525560595630Tooltip
min: 324     avg: 352.5     median: 352.5 (4%)     max: 381 Points
020406080100120140160180200220240260280300320Tooltip
Cinebench R15 - Cinebench R15 CPU Single 64 Bit
min: 166     avg: 167.5     median: 167.5 (57%)     max: 169 Points
min: 156     avg: 157.7     median: 157.7 (54%)     max: 159.3 Points
min: 124.3     avg: 138.7     median: 138.7 (47%)     max: 153 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%)
19620 MIPS (14%)
9489 MIPS (7%)
7-Zip 18.03 - 7-Zip 18.03 Single Thread 4 runs
4276 MIPS (61%)
4083 MIPS (59%)
3752 MIPS (54%)
X264 HD Benchmark 4.0 - x264 Pass 2
45.7 fps (21%)
X264 HD Benchmark 4.0 - x264 Pass 1
190 fps (52%)
HWBOT x265 Benchmark v2.2 - HWBOT x265 4k Preset
6 fps (13%)
012345678910111213Tooltip
5.3 fps (11%)
0123456789101112Tooltip
2.9 fps (6%)
012345Tooltip
Blender - Blender 2.79 BMW27 CPU *
627 Seconds (4%)
714 Seconds (5%)
1328 Seconds (9%)
R Benchmark 2.5 - R Benchmark 2.5 *
0.9 sec (19%)
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
7866 Points (27%)
4921 Points (17%)
3DMark - 3DMark Ice Storm Physics
21476 Points (14%)
3DMark - 3DMark Ice Storm Extreme Physics
21581 Points (18%)
3DMark - 3DMark Ice Storm Unlimited Physics
24185 Points (20%)
3DMark - 3DMark Cloud Gate Physics
7017 Points (18%)
3604 Points (9%)
3DMark - 3DMark Fire Strike Standard Physics
10411 Points (26%)
8936 Points (22%)
5138 Points (13%)
3DMark - 3DMark Time Spy CPU
3439 Points (18%)
2740 Points (15%)
min: 1932     avg: 2134     median: 2134 (11%)     max: 2336 Points
Geekbench 5.4 - Geekbench 5.1 - 5.4 64 Bit Single-Core
948 Points (46%)
888 Points (43%)
Geekbench 5.4 - Geekbench 5.1 - 5.4 64 Bit Multi-Core
3858 Points (13%)
1880 Points (7%)
Geekbench 5.0 - Geekbench 5.0 64 Bit Single-Core
989 Points (50%)
Geekbench 5.0 - Geekbench 5.0 64 Bit Multi-Core
4181 Points (13%)
Geekbench 4.1 - 4.4 - Geekbench 4.1 - 4.4 64 Bit Single-Core
4850 Points (56%)
4608 Points (53%)
4540 Points (52%)
Geekbench 4.1 - 4.4 - Geekbench 4.1 - 4.4 64 Bit Multi-Core
17643 Points (22%)
16580 Points (20%)
8974 Points (11%)
Mozilla Kraken 1.1 - Kraken 1.1 Total Score *
740 ms (1%)
min: 901     avg: 914     median: 913.5 (1%)     max: 926 ms
1199 ms (1%)
Octane V2 - Octane V2 Total Score
44259 Points (46%)
min: 38704     avg: 39388     median: 39387.5 (41%)     max: 40071 Points
WebXPRT 3 - WebXPRT 3 Score
210 Points (55%)
131.3 Points (35%)
Power Consumption - Prime95 Power Consumption - external Monitor *
35.9 Watt (6%)
05101520253035Tooltip
Power Consumption - Cinebench R15 Multi Power Consumption - external Monitor *
32.4 Watt (9%)
05101520253035Tooltip
Power Consumption - Cinebench R15 Multi Power Efficiency - external Monitor
10 Points per Watt (12%)

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

Average Benchmarks Intel Core i5-8257U → 91% n=13

Average Benchmarks Intel Core i3-8109U → 68% n=13

- 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 07. 18:28:41

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

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

#2 checking url part for id 10066 +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 Thu, 07 Jul 2022 13:13:06 +0200 +0s ... 0s

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

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

#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 no uid found +0.002s ... 0.009s

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

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

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

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

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

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

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

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

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

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

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

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

#25 got single benchmarks 11503 +0.007s ... 0.017s

#26 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.019s

#27 getting avg benchmarks for device 11433 +0.002s ... 0.021s

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

#29 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.022s

#30 got single benchmarks 11433 +0.006s ... 0.028s

#31 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.03s

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

#33 getting avg benchmarks for device 10066 +0s ... 0.032s

#34 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.032s

#35 got single benchmarks 10066 +0.006s ... 0.038s

#36 got avg benchmarks for devices +0s ... 0.038s

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

#38 linkCache_getLink no uid found +0.001s ... 0.038s

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

#40 linkCache_getLink no uid found +0.001s ... 0.039s

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

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

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

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

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

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

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

#48 linkCache_getLink no uid found +0.009s ... 0.05s

#49 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

#50 linkCache_getLink using $NBC_LINKCACHE +0.008s ... 0.058s

#51 linkCache_getLink no uid found +0s ... 0.058s

#52 linkCache_getLink using $NBC_LINKCACHE +0.005s ... 0.062s

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

#54 linkCache_getLink no uid found +0s ... 0.063s

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

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

#57 linkCache_getLink no uid found +0s ... 0.063s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#74 linkCache_getLink using $NBC_LINKCACHE +0.011s ... 0.08s

#75 linkCache_getLink using $NBC_LINKCACHE +0.011s ... 0.091s

#76 linkCache_getLink using $NBC_LINKCACHE +0.013s ... 0.103s

#77 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.104s

#78 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.105s

#79 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.105s

#80 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.106s

#81 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.106s

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

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

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

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

#86 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.109s

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

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

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

#90 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.11s

#91 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.111s

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

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

#94 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.112s

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

#96 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.113s

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

#98 linkCache_getLink no uid found +0.001s ... 0.113s

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

#100 linkCache_getLink no uid found +0.001s ... 0.114s

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

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

#103 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.115s

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

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

#106 linkCache_getLink no uid found +0s ... 0.116s

#107 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.117s

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

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

#110 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.118s

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

#112 linkCache_getLink no uid found +0s ... 0.118s

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

#114 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.119s

#115 linkCache_getLink no uid found +0s ... 0.119s

#116 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.119s

#117 linkCache_getLink no uid found +0.001s ... 0.12s

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

#119 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.121s

#120 linkCache_getLink using $NBC_LINKCACHE +0.006s ... 0.127s

#121 linkCache_getLink using $NBC_LINKCACHE +0.006s ... 0.133s

#122 min, max, avg, median took s +0s ... 0.133s

#123 return log +0s ... 0.133s

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)