The AMD A10-8700P is a mid-range Carrizo APU of 2015 for mainstream laptops. It is a SoC containing two Excavator CPU modules (with 4 integer and 2 FP units counted as 4 compute cores), a Radeon R7 graphics card with 6 compute cores (384 shaders), a DDR3-2133 (35 Watt cTDP) memory controller and a video engine (including UVD 6 with hardware HEVC / H.265 decoding).
The performances of the CPU and GPU cores depend on the configurable TDP. This cTDP can range from 12 to 35 Watts depending on the cooling solution and size of the laptop. Thus, clock speeds of the compute cores will vary. E.g., the GPU can score between 1764 points (15 Watts) to 2359 points (+34% with 35 Watt cTDP) in 3DMark 11 (P). CPU performance with a 35 Watt cTDP should be slightly above the Kaveri A10-7400P. If configured at 15 Watts, the CPU should be clearly slower as the Boost speed cannot be maintained for extended periods.
The AMD Pro A6-8500B is a low-end Carrizo APU (6th APU generation) of 2015 for business laptops. It is a SoC that contains one Excavator CPU modules (with 2 integer and 1 FP units counted as 2 compute cores), a Radeon R7 graphics card with 4 compute cores (256 shaders), a DDR3-1600 (not confirmed) memory controller and a video engine (including UVD 6 with hardware HEVC / H.265 decoding).
The AMD Pro A6-8500B is similar to the consumer version, the A6-8500P, but offers business support and a ensure a long-tail support program.
Due to the single module configuration, the Pro A6-8500B is a lot slower than the other Carrizo models with two modules (four cores). While the single thread performance should be similar to a Core i3-4030U, the Multi-Threading scores are only comparable to a Celeron N2940. For low demanding tasks like office and web-browsing, the performance however should be sufficient. The performance should be identical to the consumer version AMD A6-8500P.
- 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
log 21. 16:52:31
#0 checking url part for id 6845 +0s ... 0s
#1 checking url part for id 7090 +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 Mon, 20 Sep 2021 13:09:15 +0200 +0s ... 0s
#4 composed specs +0.01s ... 0.011s
#5 did output specs +0s ... 0.011s
#6 getting avg benchmarks for device 6845 +0.001s ... 0.011s
#7 got single benchmarks 6845 +0.017s ... 0.029s
#8 getting avg benchmarks for device 7090 +0s ... 0.029s
#9 got single benchmarks 7090 +0s ... 0.029s
#10 got avg benchmarks for devices +0s ... 0.029s
#11 min, max, avg, median took s +0.021s ... 0.05s