Notebookcheck
, , , , , ,
search relation.
, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
 

Intel Core i5-8279U

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.

SeriesIntel Coffee Lake
CodenameCoffee Lake-U
Series: Coffee Lake Coffee Lake-U
Intel Core i7-8559U compare2.7 - 4.5 GHz4 / 88 MB
Intel Core i7-8557U compare1.7 - 4.5 GHz4 / 88 MB
Intel Core i5-8269U compare2.6 - 4.2 GHz4 / 86 MB
» Intel Core i5-8279U2.4 - 4.1 GHz4 / 86 MB
Intel Core i5-8259U compare2.3 - 3.8 GHz4 / 86 MB
Intel Core i5-8257U compare1.4 - 3.9 GHz4 / 86 MB
Intel Core i3-8109U compare3 - 3.6 GHz2 / 44 MB
Clock Rate2400 - 4100 MHz
Level 1 Cache256 KB
Level 2 Cache1 MB
Level 3 Cache6 MB
Number of Cores / Threads4 / 8
Power Consumption (TDP = Thermal Design Power)28 Watt
Manufacturing Technology14 nm
Max. Temperature100 °C
SocketFCBGA1528
FeaturesDual-Channel DDR4 Memory Controller, HyperThreading, AVX, AVX2, Quick Sync, Virtualization, AES-NI, Intel SSE4.1, Intel SSE 4.2
GPUIntel Iris Plus Graphics 655 (300 - 1150 MHz)
64 Bit64 Bit support
Architecturex86
Announcement Date04/03/2019
Product Link (external)Intel Coffee Lake i5-8279U

Benchmarks

Cinebench R15 - Cinebench R15 CPU Multi 64 Bit
min: 743     avg: 750     median: 750 (8%)     max: 757 Points
04080120160200240280320360400440480520560600640680720Tooltip
HWBOT x265 Benchmark v2.2 - HWBOT x265 4k Preset
6 fps (13%)
012345678910111213Tooltip
- Range of benchmark values for this graphics card
- Average benchmark values for this graphics card
* Smaller numbers mean a higher performance

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 24. 01:50:37

#0 no ids found in url (should be separated by "_") +0s ... 0s

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

#2 did not recreate cache, as it is less than 5 days old! Created at Wed, 19 Jan 2022 17:37:36 +0100 +0.001s ... 0.001s

#3 linkCache_getLink no uid found +0.008s ... 0.009s

#4 composed specs +0.002s ... 0.011s

#5 did output specs +0s ... 0.011s

#6 getting avg benchmarks for device 11503 +0.001s ... 0.011s

#7 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.012s

#8 got single benchmarks 11503 +0.007s ... 0.02s

#9 got avg benchmarks for devices +0s ... 0.02s

#10 linkCache_getLink using $NBC_LINKCACHE +0.011s ... 0.03s

#11 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.033s

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

#13 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.033s

#14 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.034s

#15 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.036s

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

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

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

#19 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.038s

#20 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.04s

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

#22 linkCache_getLink using $NBC_LINKCACHE +0.003s ... 0.043s

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

#24 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.043s

#25 linkCache_getLink using $NBC_LINKCACHE +0.004s ... 0.048s

#26 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.048s

#27 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.048s

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

#29 linkCache_getLink using $NBC_LINKCACHE +0.018s ... 0.066s

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

#31 linkCache_getLink using $NBC_LINKCACHE +0.003s ... 0.07s

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

#33 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.07s

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

#35 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.07s

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

#37 linkCache_getLink using $NBC_LINKCACHE +0.005s ... 0.074s

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

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

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

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

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

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

#44 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.077s

#45 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.078s

#46 linkCache_getLink using $NBC_LINKCACHE +0.003s ... 0.082s

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

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

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

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

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

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

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

#54 linkCache_getLink using $NBC_LINKCACHE +0.003s ... 0.085s

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

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

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

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

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

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

#61 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.087s

#62 linkCache_getLink using $NBC_LINKCACHE +0.003s ... 0.09s

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

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

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

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

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

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

#69 linkCache_getLink using $NBC_LINKCACHE +0.005s ... 0.095s

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

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

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

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

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

#75 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.098s

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

#77 linkCache_getLink using $NBC_LINKCACHE +0.004s ... 0.102s

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

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

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

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

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

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

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

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

#86 linkCache_getLink using $NBC_LINKCACHE +0.003s ... 0.105s

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

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

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

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

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

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

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

#94 linkCache_getLink using $NBC_LINKCACHE