Notebookcheck Logo

AMD E2-9010 vs AMD A6-9220

AMD E2-9010

► remove from comparison AMD E2-9010

The AMD E2-9010 is the least powerful chip from the Stoney-Ridge APU series for notebooks (7th APU generation) at the time of announcement in mid 2016. The SoC integrates two CPU cores (one Excavator module with 2 integer and on FP unit) clocked between 2.0-2.2 GHz. It also includes a Radeon R2 GPU clocked at 600 MHz as well as a single-channel DDR4-1866 memory controller, H.265 video engine and chipset with all I/O ports.

Architecture

Stoney Ridge is the successor of the Carrizo architecture and the design is almost identical. Thanks to optimized manufacturing processes and more aggressive Boost behavior, however, the clocks are a bit higher at the same power consumption. The memory controller now also supports DDR4-RAM, in this case up to 1866 MHz. Stoney Ridge is the designation for the smaller dual-core and single-core chip, while Bristol Ridge is the bigger quad-core chip with dual-channel memory controller. More technical details are available in the following articles:

Power Consumption

AMD specifies the TDP of the E2-9010 with 15 Watts, but it can be configured between 10-15 Watts. This means the APU is intended for thin and light notebooks.

AMD A6-9220

► remove from comparison AMD A6-9220

The AMD A6-9220 is an entry-level chip from the Stoney-Ridge APU series for notebooks (7th APU generation), which was announced mid 2016. The 9210 is a mid-range Stoney Ridge processor (dual-core version of Bristol Ridge) and integrates two CPU cores (one Excavator module with 2 integer and on FP unit) clocked between 2.5 - 2.9 GHz. It also includes a Radeon R4 GPU, probably with 192 shaders at 655 MHz, as well as a single-channel DDR4-2133 memory controller, H.265 video engine and chipset with all I/O ports.

Architecture

Stoney Ridge is the successor of the Carrizo architecture and the design is almost identical. Thanks to optimized manufacturing processes and more aggressive Boost behavior, however, the clocks are a bit higher at the same power consumption. The memory controller now also supports DDR4-RAM, in this case up to 2133 MHz. Stoney Ridge is the designation for the smaller dual-core and single-core chip, while Bristol Ridge is the bigger quad-core chip with dual-channel memory controller. More technical details are available in the following articles:

Performance

Because of the significantly lower clock range, the A6-9220 should be noticeably slower than the A9-9410. In the Cinebench R15 Multi benchmark e.g. it was around 15% slower in our benchmarks (see below). The single core benchmarks were quite similar overall.

Graphics Card

The integrated Radeon R4 (Stoney Ridge) GPU is probably similar to the R5 with 192 active shader units (3 compute cores), but a reduced clock of just 655 instead of 800 MHz. More details about the GPU are available in the linked articles above. 

Power Consumption

AMD specifies the TDP of the A6-9220 with 15 Watts, but it can be configured between 10-15 Watts. This means the APU is a good choice for thin and light notebooks.

ModelAMD E2-9010AMD A6-9220
SeriesAMD Bristol RidgeAMD Bristol Ridge
CodenameStoney RidgeStoney Ridge
Series: Bristol Ridge Stoney Ridge
AMD A9-9425 compare3.1 - 3.7 GHz2 / 2
AMD A9-9420e compare0 - 2.5 GHz2 / 2
AMD A9-9420 compare3 - 3.6 GHz2 / 2
AMD A9-9410 compare2.9 - 3.5 GHz2 / 2
AMD A6-9225 compare2.6 - 3.1 GHz2 / 2
AMD A6-92202.5 - 2.9 GHz2 / 2
AMD A6-9220C compare1.8 - 2.7 GHz2 / 2
AMD A6-9210 compare2.4 - 2.8 GHz2 / 2
AMD A4-9120 compare2.2 - 2.5 GHz2 / 2
AMD A4-9120C compare1.6 - 2.4 GHz2 / 2
» AMD E2-90102 - 2.2 GHz2 / 2
AMD E2-9000 compare1.8 - 2.2 GHz2 / 2
AMD A6-9220e compare1.6 - 2.4 GHz2 / 2
AMD A9-9425 compare3.1 - 3.7 GHz2 / 2
AMD A9-9420e compare0 - 2.5 GHz2 / 2
AMD A9-9420 compare3 - 3.6 GHz2 / 2
AMD A9-9410 compare2.9 - 3.5 GHz2 / 2
AMD A6-9225 compare2.6 - 3.1 GHz2 / 2
» AMD A6-92202.5 - 2.9 GHz2 / 2
AMD A6-9220C compare1.8 - 2.7 GHz2 / 2
AMD A6-9210 compare2.4 - 2.8 GHz2 / 2
AMD A4-9120 compare2.2 - 2.5 GHz2 / 2
AMD A4-9120C compare1.6 - 2.4 GHz2 / 2
AMD E2-90102 - 2.2 GHz2 / 2
AMD E2-9000 compare1.8 - 2.2 GHz2 / 2
AMD A6-9220e compare1.6 - 2.4 GHz2 / 2
Clock2000 - 2200 MHz2500 - 2900 MHz
L2 Cache1 MB1 MB
Cores / Threads2 / 22 / 2
TDP10-15 Watt10-15 Watt
Transistors1200 Million1200 Million
Technology28 nm28 nm
Die Size124.5 mm2124.5 mm2
max. Temp.90 °C90 °C
SocketBGABGA
FeaturesSingle-Channel DDR4-2133, Virtualization,Single-Channel DDR4-2133, Virtualization,
iGPUAMD Radeon R2 (Stoney Ridge) ( - 600 MHz)AMD Radeon R4 (Stoney Ridge) ( - 655 MHz)
Architecturex86x86
Announced
ManufacturerAMD Bristol Ridge E2-9010AMD Bristol Ridge A6-9220
L1 Cache160 KB

Benchmarks

Cinebench R15 - Cinebench R15 CPU Multi 64 Bit
91 Points (1%)
051015202530354045505560657075808590Tooltip
min: 109     avg: 111.5     median: 111.5 (1%)     max: 114 Points
0102030405060708090100110Tooltip
Cinebench R15 - Cinebench R15 CPU Single 64 Bit
53 Points (16%)
min: 68     avg: 68.5     median: 68.5 (21%)     max: 69 Points
Cinebench R11.5 - Cinebench R11.5 CPU Multi 64 Bit
1.1 Points (2%)
1.4 Points (3%)
Cinebench R11.5 - Cinebench R11.5 CPU Single 64 Bit
0.6 Points (2%)
0.8 Points (3%)
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
1871 Points (17%)
2432 Points (22%)
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
3268 Points (4%)
3941 Points (5%)
wPrime 2.10 - wPrime 2.0 1024m *
1142 s (13%)
915 s (11%)
wPrime 2.10 - wPrime 2.0 32m *
37.1 s (7%)
27.7 s (6%)
WinRAR - WinRAR 4.0
769 Points (4%)
770 Points (4%)
X264 HD Benchmark 4.0 - x264 Pass 2
7.4 fps (3%)
8.7 fps (4%)
X264 HD Benchmark 4.0 - x264 Pass 1
39.2 fps (10%)
46.5 fps (12%)
TrueCrypt - TrueCrypt Serpent
0.1 GB/s (0%)
0.1 GB/s (0%)
TrueCrypt - TrueCrypt Twofish
0.1 GB/s (0%)
0.2 GB/s (0%)
TrueCrypt - TrueCrypt AES
0.7 GB/s (0%)
1 GB/s (0%)
3DMark 06 - CPU - 3DMark 06 - CPU
100%
1 A6-9220 +
2253 Points (5%)
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
27.9 s (6%)
20.9 s (5%)
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
61.5 s (3%)
46.9 s (2%)
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
1296 s (6%)
1022 s (5%)
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
100%
1 A6-9220 +
4236 Points (4%)
3DMark 11 - 3DM11 Performance Physics
1241 Points (4%)
min: 1467     avg: 1470     median: 1469.5 (5%)     max: 1472 Points
3DMark - 3DMark Ice Storm Physics
100%
1 A6-9220 +
16010 Points (10%)
3DMark - 3DMark Ice Storm Extreme Physics
100%
1 A6-9220 +
15125 Points (13%)
3DMark - 3DMark Ice Storm Unlimited Physics
12726 Points (11%)
15704 Points (13%)
3DMark - 3DMark Cloud Gate Physics
919 Points (2%)
1241 Points (3%)
3DMark - 3DMark Fire Strike Standard Physics
1268 Points (3%)
1721 Points (4%)
3DMark - 3DMark Time Spy CPU
100%
1 A6-9220 +
634 Points (3%)
Geekbench 4.1 - 4.4 - Geekbench 4.1 - 4.4 64 Bit Single-Core
1610 Points (18%)
1960 Points (21%)
Geekbench 4.1 - 4.4 - Geekbench 4.1 - 4.4 64 Bit Multi-Core
2402 Points (3%)
2857 Points (4%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Single-Core
1512 Points (23%)
1885 Points (29%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Multi-Core
2307 Points (6%)
2805 Points (7%)
Geekbench 3 - Geekbench 3 32 Bit Multi-Core
2348 Points (4%)
2921 Points (5%)
Geekbench 3 - Geekbench 3 32 Bit Single-Core
1415 Points (28%)
1798 Points (35%)
Geekbench 3 - Geekbench 3 64 Bit Multi-Core
2484 Points (4%)
3115 Points (5%)
Geekbench 3 - Geekbench 3 64 Bit Single-Core
1516 Points (25%)
1909 Points (31%)
Geekbench 2 - 32 Bit - Geekbench Stream
3104 Points (25%)
3245 Points (26%)
Geekbench 2 - 32 Bit - Geekbench Memory
2675 Points (24%)
2855 Points (26%)
Geekbench 2 - 32 Bit - Geekbench Floating Point
3377 Points (7%)
3510 Points (7%)
Geekbench 2 - 32 Bit - Geekbench Integer
2957 Points (6%)
3822 Points (8%)
Geekbench 2 - 32 Bit - Geekbench Total Score
3062 Points (8%)
3461 Points (9%)
Mozilla Kraken 1.1 - Kraken 1.1 Total Score *
3043 ms (4%)
2416 ms (3%)
Sunspider - Sunspider 1.0 Total Score *
234.5 ms (3%)
162.1 ms (2%)
Octane V2 - Octane V2 Total Score
10419 Points (11%)
14724 Points (15%)

Average Benchmarks AMD E2-9010 → 100% n=37

Average Benchmarks AMD A6-9220 → 119% n=37

- 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 02. 02:23:51

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

#1 checking url part for id 9326 +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 Fri, 30 Sep 2022 13:14:19 +0200 +0s ... 0s

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

#5 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.008s

#6 linkCache_getLink no uid found +0.004s ... 0.011s

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

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

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

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

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

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

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

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

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

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

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

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

#19 composed specs +0s ... 0.012s

#20 did output specs +0s ... 0.012s

#21 getting avg benchmarks for device 8183 +0s ... 0.012s

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

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

#24 got single benchmarks 8183 +0.007s ... 0.02s

#25 getting avg benchmarks for device 9326 +0s ... 0.02s

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

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

#28 got single benchmarks 9326 +0.008s ... 0.029s

#29 got avg benchmarks for devices +0s ... 0.029s

#30 linkCache_getLink no uid found +0s ... 0.029s

#31 linkCache_getLink no uid found +0.017s ... 0.046s

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

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

#34 linkCache_getLink no uid found +0s ... 0.047s

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

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

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

#38 linkCache_getLink no uid found +0s ... 0.049s

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

#40 linkCache_getLink no uid found +0s ... 0.049s

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

#42 linkCache_getLink no uid found +0.001s ... 0.05s

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

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

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

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

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

#48 linkCache_getLink no uid found +0s ... 0.053s

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

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

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

#52 linkCache_getLink no uid found +0s ... 0.054s

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

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

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

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

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

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

#59 linkCache_getLink no uid found +0s ... 0.057s

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

#61 linkCache_getLink no uid found +0s ... 0.057s

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

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

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

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

#66 linkCache_getLink no uid found +0s ... 0.059s

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

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

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

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

#71 linkCache_getLink no uid found +0s ... 0.061s

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

#73 linkCache_getLink no uid found +0s ... 0.062s

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

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

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

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

#78 linkCache_getLink no uid found +0s ... 0.064s

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

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

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

#82 linkCache_getLink no uid found +0s ... 0.065s

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

#84 linkCache_getLink no uid found +0s ... 0.066s

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

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

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

#88 linkCache_getLink no uid found +0s ... 0.067s

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

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

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

#92 linkCache_getLink no uid found +0s ... 0.069s

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

#94 linkCache_getLink no uid found +0s ... 0.069s

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

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

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

#98 linkCache_getLink no uid found +0s ... 0.071s

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

#100 linkCache_getLink no uid found +0s ... 0.072s

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

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

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

#104 linkCache_getLink no uid found +0s ... 0.073s

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

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

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

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

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

#110 min, max, avg, median took s +0s ... 0.075s

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

#112 return log +0.004s ... 0.079s

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)