Notebookcheck Logo

Apple A13 Bionic vs Intel Core i5-8210Y

Apple A13 Bionic

► remove from comparison Apple A13 Bionic

The Apple A13 Bionic is a System on a Chip (SoC) from Apple that is found in the iPhone 11 series. It was announced late 2019 and offers 6 cores divided in 2 performance cores and four power efficiency cores. Compared to the previous A12 Bionic, the A13 should offer a 20% improved CPU performance at 40% lower power (according to Apple).

With 8.5 billion transistors, the A13 Bionic is a big chip especially compared to the Snapdragon 835 (3 Billion) or a Skylake desktop quad-core Soc (1.75 Billion).

Intel Core i5-8210Y

► remove from comparison

The Intel Core i5-8210Y is a very efficient dual-core SoC for (passively) cooled notebooks based on the Amber Lake generation and was announced on 30th October 2018 with the new MacBook Air. The CPU consists of two processor cores clocked at 1.6 - 3.6 GHz and a TDP of 7 Watt. Thanks to Hyper Threading, the processor can execute up to four threads simultaneously. The chips also includes the Intel HD Graphics 617 GPU, a dual-channel memory controller (DDR3L/LPDDR3) as well as VP9 and H.265 video de- and encoder. Compared to the Kaby Lake-Y predecessors (e.g. Core i7-7Y75), Amber Lake uses the same architecture produced in the improved 14nm+ FinFET process (no 14nm++) but offers higher clock speeds at an increased TDP rating. The Core i5-8200Y is very similar when configured to 7 Watt (cTDP up) and offers even higher Turbo clocks, but a slightly slower GPU (-100 MHz).

Architecture

Intel basically used the familiar micro architecture from the Skylake / Kaby Lake generation, so the per-MHz performance is identical.

Performance

The performance of the Y series is highly depending on the cooling solution of the laptop / tablet and the TDP settings for sustained load. Therefore, the differences between a Core m3 and a i7 may be rather slim, if the thermals are very limited. The high Turbo clock speeds in Amber Lake should however lead to a very good single thread performance for short bursts.

Graphics

The integrated Intel HD Graphics 617 GPU has 24 Execution Units (EUs) like the old HD Graphics 515 and runs with clocks between 300 and 1050 MHz in combination with this processor. The performance heavily depends on the TDP limit as well as the memory configuration; with fast LPDDR3-1866 RAM in dual-channel mode, the GPU should sometimes be able to compete with the HD Graphics 520, but can also be much slower in other scenarios. Modern games from 2016 will, if at all, only run smoothly in the lowest settings.

Contrary to Skylake, Kaby Lake and Amber Lake now also supports hardware decoding for H.265/HEVC Main10 with a 10-bit color depth as well as Google's VP9 codec.

Power Consumption

The chip is manufactured in the 14 nm+ process with FinFET transistors. The typical TDP for the Amber Lake Y-series is specified at 5 Watts, but the i5-8210Y is specified at 7 Watt (for the MacBook Air).

ModelApple A13 BionicIntel Core i5-8210Y
SeriesApple Apple A-SeriesIntel Amber Lake
CodenameLightning and ThunderAmber Lake-Y
Clock <=2660 MHz1600 - 3600 MHz
L1 Cache832 KB128 KB
L2 Cache12 MB512 KB
Cores / Threads6 / 62 / 4
Transistors6900 Million
Technology7 nm14 nm
FeaturesARMv8 Instruction SetDual-Channel DDR3L-1600/LPDDR3-2133 Memory Controller (16 GB max), HyperThreading, AVX, AVX2, Quick Sync, Virtualization, AES-NI, vPro, TXT
iGPUApple A13 Bionic GPUIntel UHD Graphics 617 (300 - 1050 MHz)
ArchitectureARMx86
Announced
Series: Amber Lake Amber Lake-Y
Intel Core i7-8500Y compare1.5 - 4.2 GHz2 / 44 MB
» Intel Core i5-8210Y1.6 - 3.6 GHz2 / 44 MB
Intel Core i5-8200Y compare1.3 - 3.9 GHz2 / 44 MB
Intel Core i3-10100Y compare1.3 - 3.9 GHz2 / 44 MB
Intel Core m3-8100Y compare1.1 - 3.4 GHz2 / 44 MB
Intel Pentium Gold 6500Y compare1.1 - 3.4 GHz2 / 44 MB
L3 Cache4 MB
TDP7 Watt
max. Temp.100 °C
SocketBGA
$281 U.S.
ManufacturerIntel Amber Lake i5-8210Y

Benchmarks

Performance Rating - CB R15 + R20 + 7-Zip + X265 + Blender + 3DM11 CPU - i5-8210Y
27.9 pt (33%)
Cinebench R20 - Cinebench R20 CPU (Single Core)
312 Points (40%)
Cinebench R20 - Cinebench R20 CPU (Multi Core)
601 Points (3%)
Cinebench R15 - Cinebench R15 CPU Multi 64 Bit
min: 254     avg: 269.5     median: 269.5 (3%)     max: 285 Points
0153045607590105120135150165180195210225240255270285Tooltip
Cinebench R15 - Cinebench R15 CPU Single 64 Bit
min: 127     avg: 129.5     median: 129.5 (44%)     max: 132 Points
7-Zip 18.03 - 7-Zip 18.03 Multli Thread 4 runs
7936 MIPS (6%)
7-Zip 18.03 - 7-Zip 18.03 Single Thread 4 runs
3405 MIPS (49%)
HWBOT x265 Benchmark v2.2 - HWBOT x265 4k Preset
2.3 fps (5%)
012345Tooltip
Blender - Blender 2.79 BMW27 CPU *
1680 Seconds (12%)
3DMark 06 - CPU - 3DMark 06 - CPU
3544 Points (8%)
3DMark 11 - 3DM11 Performance Physics
min: 3311     avg: 3571     median: 3571 (12%)     max: 3831 Points
3DMark - 3DMark Ice Storm Unlimited Physics
min: 33851     avg: 33885     median: 33881 (29%)     max: 33925 Points
17419 Points (15%)
3DMark - 3DMark Cloud Gate Physics
2252 Points (6%)
3DMark - 3DMark Fire Strike Standard Physics
min: 3028     avg: 3110     median: 3110 (8%)     max: 3192 Points
3DMark - 3DMark Time Spy CPU
min: 1194     avg: 1205     median: 1204.5 (6%)     max: 1215 Points
3DMark - 3DMark Sling Shot Extreme (ES 3.1) Unlimited Physics
min: 2078     avg: 2803     median: 2958 (37%)     max: 3219 Points
3DMark - 3DMark Sling Shot (ES 3.0) Unlimited Physics
min: 3411     avg: 3780     median: 3877 (56%)     max: 4052 Points
Geekbench 5.4 - Geekbench 5.1 - 5.4 64 Bit Single-Core
min: 1326     avg: 1333     median: 1332 (65%)     max: 1342 Points
Geekbench 5.4 - Geekbench 5.1 - 5.4 64 Bit Multi-Core
min: 3235     avg: 3381     median: 3378.5 (12%)     max: 3531 Points
Geekbench 5.0 - Geekbench 5.0 64 Bit Single-Core
min: 1343     avg: 1343     median: 1343 (68%)     max: 1344 Points
660 Points (34%)
Geekbench 5.0 - Geekbench 5.0 64 Bit Multi-Core
min: 3242     avg: 3427     median: 3463 (11%)     max: 3575 Points
1433 Points (5%)
Geekbench 4.1 - 4.4 - Geekbench 4.1 - 4.4 64 Bit Single-Core
4162 Points (48%)
Geekbench 4.1 - 4.4 - Geekbench 4.1 - 4.4 64 Bit Multi-Core
7474 Points (9%)
Mozilla Kraken 1.1 - Kraken 1.1 Total Score *
min: 545     avg: 562     median: 571 (1%)     max: 573 ms
min: 817     avg: 906     median: 906 (1%)     max: 995 ms
Octane V2 - Octane V2 Total Score
min: 47288     avg: 48727     median: 48991 (51%)     max: 49388 Points
min: 29470     avg: 33003     median: 33003 (34%)     max: 36536 Points
WebXPRT 3 - WebXPRT 3 Score
min: 146     avg: 179.2     median: 183 (48%)     max: 202 Points
AnTuTu v7 - AnTuTu v7 MEM
min: 10494     avg: 12510     median: 12592 (39%)     max: 14443 Points
AnTuTu v7 - AnTuTu v7 UX
min: 77118     avg: 77810     median: 78032 (96%)     max: 78279 Points
AnTuTu v7 - AnTuTu v7 GPU
min: 218738     avg: 219891     median: 218937 (68%)     max: 221998 Points
AnTuTu v7 - AnTuTu v7 CPU
min: 147281     avg: 149542     median: 148191 (91%)     max: 153154 Points
AnTuTu v7 - AnTuTu v7 Total Score
min: 456891     avg: 459752     median: 459850 (81%)     max: 462516 Points
AnTuTu v8 - AnTuTu v8 UX
min: 64361     avg: 75201     median: 78294 (65%)     max: 82947 Points
AnTuTu v8 - AnTuTu v8 MEM
min: 67691     avg: 75819     median: 74262 (60%)     max: 85504 Points
AnTuTu v8 - AnTuTu v8 GPU
min: 190559     avg: 203672     median: 209164 (38%)     max: 211292 Points
AnTuTu v8 - AnTuTu v8 CPU
min: 149088     avg: 156731     median: 152919 (55%)     max: 168185 Points
AnTuTu v8 - AnTuTu v8 Total Score
min: 489463     avg: 511422     median: 510245 (49%)     max: 534558 Points
Antutu v9 - AnTuTu v9 Total Score
622382 Points (52%)
Antutu v9 - AnTuTu v9 CPU
147649 Points (6%)
PassMark PerformanceTest Mobile V1 - PerformanceTest Mobile CPU Tests
min: 650706     avg: 678820     median: 683897 (90%)     max: 701856 Points
CrossMark - CrossMark Overall
min: 776     avg: 835     median: 849 (37%)     max: 864 Points
Power Consumption - Geekbench 5.4 Power Consumption 150cd *
7 Watt (31%)
012345678910111213Tooltip
Power Consumption - Idle Power Consumption 150cd *
2.9 Watt (9%)
00.10.30.40.60.70.911.21.31.51.61.81.92.12.22.42.52.72.8Tooltip

Average Benchmarks Apple A13 Bionic → 100% n=5

Average Benchmarks Intel Core i5-8210Y → 62% n=5

- 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.18
log 30. 08:30:22

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

#1 checking url part for id 10886 +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 Sun, 25 Sep 2022 13:14:15 +0200 +0s ... 0s

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

#5 linkCache_getLink no uid found +0.003s ... 0.008s

#6 composed specs +0.001s ... 0.009s

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

#8 getting avg benchmarks for device 11496 +0.001s ... 0.01s

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

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

#11 got single benchmarks 11496 +0.011s ... 0.021s

#12 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.023s

#13 linkCache_getLink using $NBC_LINKCACHE +0.003s ... 0.026s

#14 getting avg benchmarks for device 10886 +0.002s ... 0.027s

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

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

#17 got single benchmarks 10886 +0.007s ... 0.035s

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

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

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

#21 linkCache_getLink using $NBC_LINKCACHE +0.009s ... 0.044s

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

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

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

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

#26 linkCache_getLink using $NBC_LINKCACHE +0.01s ... 0.056s

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

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

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

#30 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.058s

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

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

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

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

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

#36 linkCache_getLink using $NBC_LINKCACHE +0.005s ... 0.064s

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

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

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

#40 linkCache_getLink using $NBC_LINKCACHE +0.004s ... 0.069s

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

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

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

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

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

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

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

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

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

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

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

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

#53 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.071s

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

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

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

#57 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.072s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#82 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.077s

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

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

#85 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.077s

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

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

#88 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.078s

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

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

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

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

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

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

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

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

#97 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.081s

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

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

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

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

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

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

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

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

#106 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.083s

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

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

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

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

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

#112 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.085s

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

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

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

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

#117 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.088s

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

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

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

#121 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.089s

#122 linkCache_getLink using $NBC_LINKCACHE +0.007s ... 0.096s

#123 min, max, avg, median took s +0.002s ... 0.099s

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

#125 return log +0.004s ... 0.103s

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