Notebookcheck Logo

AMD E2-9000 vs AMD A9-9410

AMD E2-9000

► remove from comparison AMD E2-9000

The AMD E2-9000 is the least powerful chip from the Stoney-Ridge APU series for notebooks (7th APU generation) at the time of announcement in 2017. The SoC integrates two CPU cores (one Excavator module with 2 integer and on FP unit) clocked between 1.8-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. Compared to the older E2-9010, the E2-9000 offers a lower base speed (1.8 versus 2 GHz).

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-9000 with 10 Watts (compared to the 9010 at 15W). This means the APU is intended for thin and light notebooks.

AMD A9-9410

► remove from comparison AMD A9-9410

The AMD A9-9410 is an entry-level chip from the Stoney-Ridge APU series for notebooks (7th APU generation), which was announced mid 2016. At its launch, the A9-9410 is the fastest 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.9-3.5 GHz. It also includes a Radeon R5 GPU with 192 shaders at 800 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

Thanks to the high maximum clock of up to 3.5 GHz, the single-core performance should be pretty good. The multi-core performance on the other hand is much lower compared to the Bristol Ridge models. Compared to older Carrizo-L/Beema quad-cores, the APU should still perform pretty well. The level of performance should be similar to a Core-m3 and therefore also be sufficient for more demanding applications.

The TDP can be configured between 10-25 Watts, so there can be big performance differences under sustained workloads.

Graphics Card

The integrated Radeon R5 (Stoney Ridge) GPU has 192 active shader units (3 compute cores) clocked at up to 800 MHz. More details about the GPU are available in the linked articles above. 

Power Consumption

AMD specifies the TDP of the A9-9410 with 15 Watts, but it can be configured between 10-25 Watts. This means the CPU is a good choice for thin and light notebooks, but also 15-inch devices with better cooling capabilities.

ModelAMD E2-9000AMD A9-9410
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-94102.9 - 3.5 GHz2 / 2
AMD A6-9225 compare2.6 - 3.1 GHz2 / 2
AMD A6-9220 compare2.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-9010 compare2 - 2.2 GHz2 / 2
» AMD E2-90001.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-94102.9 - 3.5 GHz2 / 2
AMD A6-9225 compare2.6 - 3.1 GHz2 / 2
AMD A6-9220 compare2.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-9010 compare2 - 2.2 GHz2 / 2
AMD E2-90001.8 - 2.2 GHz2 / 2
AMD A6-9220e compare1.6 - 2.4 GHz2 / 2
Clock1800 - 2200 MHz2900 - 3500 MHz
L2 Cache1 MB1 MB
Cores / Threads2 / 22 / 2
TDP10 Watt10-25 Watt
Transistors1200 Million1200 Million
Technology28 nm28 nm
Die Size124.5 mm2124.5 mm2
max. Temp.90 °C90 °C
SocketBGABGA
FeaturesSingle-Channel DDR4-1866, Virtualization,Single-Channel DDR4-2133, Virtualization,
iGPUAMD Radeon R2 (Stoney Ridge) ( - 600 MHz)AMD Radeon R5 (Stoney Ridge) ( - 800 MHz)
Architecturex86x86
Announced
ManufacturerAMD Bristol Ridge E2-9000AMD Bristol Ridge A9-9410

Benchmarks

Cinebench R15 - Cinebench R15 CPU Multi 64 Bit
84 Points (1%)
05101520253035404550556065707580Tooltip
130 Points (1%)
0102030405060708090100110120130Tooltip
Cinebench R15 - Cinebench R15 CPU Single 64 Bit
47 Points (15%)
63 Points (19%)
Cinebench R11.5 - Cinebench R11.5 CPU Multi 64 Bit
1 Points (2%)
1.6 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)
1787 Points (16%)
2694 Points (24%)
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
2897 Points (4%)
4619 Points (6%)
wPrime 2.10 - wPrime 2.0 1024m *
1242 s (15%)
751 s (9%)
wPrime 2.10 - wPrime 2.0 32m *
36.2 s (7%)
24 s (5%)
WinRAR - WinRAR 4.0
744 Points (4%)
879 Points (5%)
X264 HD Benchmark 4.0 - x264 Pass 2
6.3 fps (3%)
10.1 fps (4%)
X264 HD Benchmark 4.0 - x264 Pass 1
35.7 fps (9%)
53.5 fps (14%)
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
1556 Points (3%)
2455 Points (5%)
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
26.9 s (6%)
17.8 s (4%)
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
59.8 s (3%)
39.8 s (2%)
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
1304 s (6%)
878 s (4%)
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
3146 Points (3%)
4764 Points (5%)
3DMark 11 - 3DM11 Performance Physics
1199 Points (4%)
1470 Points (5%)
3DMark - 3DMark Ice Storm Physics
11949 Points (8%)
17953 Points (12%)
3DMark - 3DMark Ice Storm Extreme Physics
10209 Points (8%)
17279 Points (14%)
3DMark - 3DMark Ice Storm Unlimited Physics
11528 Points (10%)
17768 Points (15%)
3DMark - 3DMark Cloud Gate Physics
914 Points (2%)
1318 Points (3%)
3DMark - 3DMark Fire Strike Standard Physics
1255 Points (3%)
2054 Points (5%)
3DMark - 3DMark Time Spy CPU
100%
1 A9-9410 +
732 Points (4%)
Geekbench 4.1 - 4.4 - Geekbench 4.1 - 4.4 64 Bit Single-Core
100%
1 E2-9000 +
1591 Points (17%)
Geekbench 4.1 - 4.4 - Geekbench 4.1 - 4.4 64 Bit Multi-Core
100%
1 E2-9000 +
2461 Points (3%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Single-Core
1543 Points (24%)
2133 Points (33%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Multi-Core
2371 Points (6%)
3182 Points (8%)
Geekbench 3 - Geekbench 3 32 Bit Multi-Core
2323 Points (4%)
3299 Points (6%)
Geekbench 3 - Geekbench 3 32 Bit Single-Core
1430 Points (28%)
2134 Points (42%)
Geekbench 3 - Geekbench 3 64 Bit Multi-Core
2439 Points (4%)
3516 Points (6%)
Geekbench 3 - Geekbench 3 64 Bit Single-Core
1526 Points (25%)
2255 Points (37%)
Geekbench 2 - 32 Bit - Geekbench Stream
2993 Points (24%)
3482 Points (28%)
Geekbench 2 - 32 Bit - Geekbench Memory
2893 Points (26%)
3458 Points (31%)
Geekbench 2 - 32 Bit - Geekbench Floating Point
2847 Points (6%)
4828 Points (9%)
Geekbench 2 - 32 Bit - Geekbench Integer
2914 Points (6%)
4375 Points (9%)
Geekbench 2 - 32 Bit - Geekbench Total Score
2894 Points (8%)
4260 Points (11%)
Mozilla Kraken 1.1 - Kraken 1.1 Total Score *
3175 ms (4%)
2081 ms (2%)
Sunspider - Sunspider 1.0 Total Score *
258.9 ms (3%)
147.7 ms (2%)
Octane V2 - Octane V2 Total Score
10575 Points (11%)
17423 Points (18%)

Average Benchmarks AMD E2-9000 → 100% n=39

Average Benchmarks AMD A9-9410 → 139% n=39

- 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 01. 13:57:21

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

#1 checking url part for id 8181 +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.006s ... 0.006s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#21 getting avg benchmarks for device 9294 +0.001s ... 0.012s

#22 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.013s

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

#24 got single benchmarks 9294 +0.009s ... 0.021s

#25 getting avg benchmarks for device 8181 +0.001s ... 0.022s

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

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

#28 got single benchmarks 8181 +0.008s ... 0.031s

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

#30 linkCache_getLink using $NBC_LINKCACHE +0.013s ... 0.044s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#59 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.057s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#105 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.074s

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

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

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

#109 min, max, avg, median took s +0s ... 0.076s

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

#111 return log +0.004s ... 0.08s

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)