Notebookcheck Logo

AMD PRO A12-9800B vs AMD PRO A12-9830B vs AMD A10-9620P

AMD PRO A12-9800B

► remove from comparison AMD PRO A12-9800B

The AMD PRO A12-9800B is a mobile mainstream SoC from the Bristol-Ridge APU series for notebooks (7th APU generation), which was announced mid 2016. It is the business version of the AMD FX-9800P and features the same specifications. The PRO A12-9800B is (together with the FX-9800P) the fastest Bristol Ridge APU with a 15-Watt TDP and the successor to the 15-Watt A12-8800B / FX-8800P from the Carrizo generation. The ULV chip has four CPU cores (two Excavator modules = 4 integer and 2 FP units), a Radeon R7 GPU as well as a dual-channel DDR4-1866 memory controller. Carrizo is a full-fledged SoC and is also equipped with an integrated chipset, which provides all I/0 ports.

Architecture

Bristol 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. More technical details are available in the following articles:

Performance

Thanks to higher clocks, the A12-9800B is slightly ahead of the old 15-Watt top model FX-8800P and competes with a Intel Core i3-6100U (Skylake, 15 Watts). Compared to the Intel model, the AMD chip has a small advantage in multi-thread scenarios, but is beaten when you only stress one or two cores.

This means there is sufficient performance for typical office and web applications as well as light multitasking.

Graphics Card

The integrated Radeon R7 (Bristol Ridge) GPU has 512 active shader units (8 compute cores) clocked at up to 758 MHz. Thanks to the better utilization of the clock range as well as faster DDR4-RAm, the GPU can slightly beat its predecessors Radeon R7 (Carrizo) and competes with a dedicated GeForce 920MX in the best-case scenario (dual-channel memory, low CPU requirements). Many games from 2015/2016 can be played smoothly at low settings. 

Power Consumption

AMD specifies the TDP of the A12-9800B with 12-15 Watts, which is comparable to Intel's ULV models. This means the APU is a good choice for thin notebooks starting with a 12-inch screen.

AMD PRO A12-9830B

► remove from comparison AMD PRO A12-9830B

The AMD PRO A12-9830B is a mobile mainstream SoC from the Bristol-Ridge APU series for notebooks (7th APU generation), which was announced mid 2016. It is the business variant of the FX-9830P. The A12-9830B / FX-9830P is the fastest Bristol Ridge APU with a 45-Watt TDP and the successor to the 15-35-Watt FX-8800P from the Carrizo generation. The chip has four CPU cores (two Excavator modules = 4 integer and 2 FP units), a Radeon R7 GPU as well as a dual-channel DDR4-1866 memory controller. Carrizo is a full-fledged SoC and is also equipped with an integrated chipset, which provides all I/0 ports.

Architecture

Bristol 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 2400 MHz. More technical details are available in the following articles:

Performance

Thanks to higher clocks, the A12-9830B is slightly ahead of the old 35-Watt top model FX-8800P and competes with the entry-level dual-cores from Intel (Skylake and Kaby Lake). Compared to the Intel model, the AMD chip has a small advantage in multi-thread scenarios, but is beaten when you only stress one or two cores.

This means there is sufficient performance for typical office and web applications as well as light multitasking.

Graphics Card

The integrated Radeon R7 (Bristol Ridge) GPU has 512 active shader units (8 compute cores) clocked at up to 900 MHz (compared to 758 MHz for FX-9800P/A12-9800B). Thanks to the better utilization of the clock range as well as faster DDR4-RAm, the GPU can slightly beat its predecessors Radeon R7 (Carrizo) and competes with a dedicated GeForce 920MX in the best-case scenario (dual-channel memory). Many games from 2015/2016 can be played smoothly at low settings. 

Power Consumption

AMD specifies the TDP of the A12-9830B with 25-45 Watts, which is comparable to Intel quad-core processors from the H-series. This means the APU is a good choice for big and heavy notebooks with at least 15 inches.

AMD A10-9620P

► remove from comparison AMD A10-9620P

The AMD A10-9620P is a mid-range APU of the Bristol Ridge series (7th generation of APUs) with 4 CPU-cores (two Excavator modules) clocked at 2.5 - 3.4 GHz. In our tests the A10-9620P even hit 3.6 GHz.

It was announced in 2017 and is based on the same silicon as Carrizo but with more and refined features. It is a ULV-chip with a TDP of 15 Watt and integrates a Radeon R5 graphics card (384 shader cores / 6 compute cores) and a dual-channel DDR4-18600 memory controller. As Carrizo its a full featured SoC that offers all I/O ports on the chip.

The A10-9620P is a bit faster than the old 15-Watt top model of Carrizo, the FX-8800P. See our Bristol Ridge article for more information on the architecture and improvements compared to Carrizo.

ModelAMD PRO A12-9800BAMD PRO A12-9830BAMD A10-9620P
SeriesAMD Bristol RidgeAMD Bristol RidgeAMD Bristol Ridge
CodenameBristol RidgeBristol RidgeBristol Ridge
Series: Bristol Ridge Bristol Ridge
AMD FX-9830P3 - 3.7 GHz4 / 4
AMD PRO A12-9830B3 - 3.7 GHz4 / 4
AMD FX-9800P2.7 - 3.6 GHz4 / 4
» AMD PRO A12-9800B2.7 - 3.6 GHz4 / 4
AMD A12-9720P2.7 - 3.6 GHz4 / 4
AMD A12-9700P2.5 - 3.4 GHz4 / 4
AMD A10-9620P2.5 - 3.4 GHz4 / 4
AMD A10-9600P2.4 - 3.3 GHz4 / 4
AMD PRO A8-9600B2.4 - 3.3 GHz4 / 4
AMD FX-9830P3 - 3.7 GHz4 / 4
» AMD PRO A12-9830B3 - 3.7 GHz4 / 4
AMD FX-9800P2.7 - 3.6 GHz4 / 4
AMD PRO A12-9800B2.7 - 3.6 GHz4 / 4
AMD A12-9720P2.7 - 3.6 GHz4 / 4
AMD A12-9700P2.5 - 3.4 GHz4 / 4
AMD A10-9620P2.5 - 3.4 GHz4 / 4
AMD A10-9600P2.4 - 3.3 GHz4 / 4
AMD PRO A8-9600B2.4 - 3.3 GHz4 / 4
AMD FX-9830P3 - 3.7 GHz4 / 4
AMD PRO A12-9830B3 - 3.7 GHz4 / 4
AMD FX-9800P2.7 - 3.6 GHz4 / 4
AMD PRO A12-9800B2.7 - 3.6 GHz4 / 4
AMD A12-9720P2.7 - 3.6 GHz4 / 4
AMD A12-9700P2.5 - 3.4 GHz4 / 4
» AMD A10-9620P2.5 - 3.4 GHz4 / 4
AMD A10-9600P2.4 - 3.3 GHz4 / 4
AMD PRO A8-9600B2.4 - 3.3 GHz4 / 4
Clock2700 - 3600 MHz3000 - 3700 MHz2500 - 3400 MHz
L2 Cache2 MB2 MB2 MB
Cores / Threads4 / 44 / 44 / 4
TDP15 Watt25-45 Watt15 Watt
Transistors3100 Million3100 Million3100 Million
Technology28 nm28 nm28 nm
Die Size250 mm2250 mm2250 mm2
max. Temp.90 °C90 °C90 °C
SocketFP4FP4
FeaturesDual-Channel DDR3/DDR4-1866 Memory Controller, PCIe 3.0 x8Dual-Channel DDR3/DDR4-1866 Memory Controller, PCIe 3.0 x8Dual-Channel DDR3/DDR4-1866 Memory Controller, PCIe 3.0 x8
iGPUAMD Radeon R7 (Bristol Ridge) ( - 758 MHz)AMD Radeon R7 (Bristol Ridge) ( - 900 MHz)AMD Radeon R5 (Bristol Ridge) ( - 758 MHz)
Architecturex86x86x86
Announced
ManufacturerAMD Bristol Ridge PRO A12-9800BAMD Bristol Ridge PRO A12-9830B

Benchmarks

Cinebench R15 - Cinebench R15 CPU Multi 64 Bit
min: 222     avg: 225.3     median: 225 (2%)     max: 229 Points
0153045607590105120135150165180195210225Tooltip
230 Points (2%)
0153045607590105120135150165180195210225Tooltip
Cinebench R15 - Cinebench R15 CPU Single 64 Bit
min: 75     avg: 75.7     median: 75 (26%)     max: 77 Points
72 Points (25%)
Cinebench R11.5 - Cinebench R11.5 CPU Multi 64 Bit
min: 2.47     avg: 2.6     median: 2.6 (5%)     max: 2.7 Points
2.7 Points (5%)
Cinebench R11.5 - Cinebench R11.5 CPU Single 64 Bit
min: 0.86     avg: 0.9     median: 0.9 (3%)     max: 0.9 Points
0.8 Points (3%)
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
min: 2564     avg: 2593     median: 2592.5 (23%)     max: 2621 Points
2277 Points (20%)
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
min: 6854     avg: 7056     median: 7055.5 (10%)     max: 7257 Points
7420 Points (10%)
Cinebench R10 - Cinebench R10 Rend. Multi (64bit)
10237 Points (9%)
Cinebench R10 - Cinebench R10 Rend. Single (64bit)
3499 Points (21%)
wPrime 2.10 - wPrime 2.0 1024m *
475.7 s (6%)
470.9 s (6%)
wPrime 2.10 - wPrime 2.0 32m *
13.8 s (3%)
14.4 s (3%)
WinRAR - WinRAR 4.0
1383 Points (8%)
X264 HD Benchmark 4.0 - x264 Pass 2
16.5 fps (7%)
16.3 fps (7%)
X264 HD Benchmark 4.0 - x264 Pass 1
77 fps (21%)
76.6 fps (21%)
TrueCrypt - TrueCrypt Serpent
0.2 GB/s (8%)
TrueCrypt - TrueCrypt Twofish
0.3 GB/s (7%)
TrueCrypt - TrueCrypt AES
1.8 GB/s (7%)
3DMark 06 - CPU - 3DMark 06 - CPU
3249 Points (7%)
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
18.6 s (4%)
18.2 s (4%)
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
41.1 s (2%)
40.3 s (2%)
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
908 s (4%)
977 s (4%)
3DMark 11 - 3DM11 Performance Physics
min: 2232     avg: 2318     median: 2275 (8%)     max: 2448 Points
2399 Points (8%)
3DMark - 3DMark Ice Storm Physics
min: 24353     avg: 25657     median: 25657 (16%)     max: 26961 Points
22553 Points (15%)
3DMark - 3DMark Ice Storm Extreme Physics
min: 25150     avg: 25871     median: 25871 (21%)     max: 26592 Points
24032 Points (20%)
3DMark - 3DMark Ice Storm Unlimited Physics
min: 27021     avg: 27778     median: 27778 (23%)     max: 28535 Points
3DMark - 3DMark Cloud Gate Physics
min: 1989     avg: 2038     median: 2035 (5%)     max: 2089 Points
2338 Points (6%)
3DMark - 3DMark Fire Strike Standard Physics
min: 2739     avg: 2999     median: 3007 (7%)     max: 3251 Points
3175 Points (8%)
3DMark - 3DMark Time Spy CPU
min: 437     avg: 439     median: 439 (2%)     max: 441 Points
Geekbench 4.0 - Geekbench 4.0 64 Bit Single-Core
2073 Points (32%)
Geekbench 4.0 - Geekbench 4.0 64 Bit Multi-Core
4453 Points (11%)
Geekbench 3 - Geekbench 3 32 Bit Multi-Core
5326 Points (9%)
Geekbench 3 - Geekbench 3 32 Bit Single-Core
2031 Points (40%)
Geekbench 3 - Geekbench 3 64 Bit Multi-Core
5575 Points (9%)
Geekbench 3 - Geekbench 3 64 Bit Single-Core
2109 Points (35%)
Geekbench 2 - 32 Bit - Geekbench Stream
3270 Points (26%)
Geekbench 2 - 32 Bit - Geekbench Memory
2974 Points (27%)
Geekbench 2 - 32 Bit - Geekbench Floating Point
7151 Points (14%)
Geekbench 2 - 32 Bit - Geekbench Integer
6518 Points (13%)
Geekbench 2 - 32 Bit - Geekbench Total Score
5705 Points (15%)
Mozilla Kraken 1.1 - Kraken 1.1 Total Score *
min: 2152     avg: 2225     median: 2159 (3%)     max: 2363 ms
Sunspider - Sunspider 1.0 Total Score *
170.4 ms (2%)
Octane V2 - Octane V2 Total Score
min: 16552     avg: 17731     median: 18206 (19%)     max: 18435 Points

Average Benchmarks AMD PRO A12-9800B → NAN% n=

Average Benchmarks AMD A10-9620P → NAN% n=

- 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 16. 13:11:13

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

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

#2 checking url part for id 9188 +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, 11 Aug 2022 13:13:36 +0200 +0s ... 0s

#5 linkCache_getLink no uid found +0.01s ... 0.01s

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

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

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

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

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

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

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

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

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

#15 linkCache_getLink no uid found +0.002s ... 0.017s

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

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

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

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

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

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

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

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

#24 composed specs +0s ... 0.017s

#25 did output specs +0s ... 0.017s

#26 getting avg benchmarks for device 8544 +0s ... 0.017s

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

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

#29 got single benchmarks 8544 +0.01s ... 0.028s

#30 getting avg benchmarks for device 8550 +0s ... 0.028s

#31 got single benchmarks 8550 +0s ... 0.028s

#32 getting avg benchmarks for device 9188 +0.001s ... 0.029s

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

#34 got single benchmarks 9188 +0.007s ... 0.036s

#35 got avg benchmarks for devices +0s ... 0.036s

#36 linkCache_getLink using $NBC_LINKCACHE +0.017s ... 0.053s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#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.065s

#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.066s

#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.067s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#115 min, max, avg, median took s +0s ... 0.074s

#116 return log +0s ... 0.074s

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)