The AMD Ryzen 3 2200G is a desktop APU that was announced in early 2018. It combines four Zen cores (4 threads as no SMT/HyperThreading support) clocked at 3.5 - 3.7 GHz with a Radeon RX Vega 8 graphics card with 8 CUs (512 of the 704 Shaders on the chip) clocked at up to 1100 MHz. The integrated dual-channel memory controller supports up to DDR-2933. The TDP is specified at 65 Watt and the CPU, GPU and memory are unlocked for overclocking. More information on Raven Ridge can be found in our launch article.
The AMD 3015Ce (Codename Dali) is a mobile APU that integrates two Zen cores (with SMT, therefore 4 threads) clocked at 1.2 to 2.3 GHz. It is the Chromebook version of the AMD 3015e with identical specifications. The integrated Radeon graphics card offers 3 CUs at up to 600 MHz (Radeon RX Vega 3). The single channel memory controller supports only DDR4-1600. The chip is manufactured in 14nm and officially counted to the 3000 series of mobile processors.
AMD compares the performance of the 3015e (and therefore also the identical 3015Ce) against the entry level Intel Celeron N4120 (Quad-Core Atom). The 3015e should be 36% faster in single thread Cinebench R20 test. This is expected as the Atom cores offer a low single thread performance. Multi-thread benchmarks were not provided, so we guess the N4120 will be faster with its 4 cores. In PCMark 10 the 3015e should be 18% faster and in the 3DMark Night Raid the integrated GPU should beat the UHD Graphics 600 in the N4120 by 24%.
More information on Raven Ridge can be found in our launch article.
Power consumption
This AMD APU has a 6 W default TDP (also known as the long-term power limit). TDP values that low are typical for affordable laptops as well as ultra-compact mini-PCs, mostly with no active cooling solution.
AMD 3015Ce is manufactured on a 14 nm process making for subpar, as of late 2022, energy efficiency.
- 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.22
log 09. 09:22:25
#0 checking url part for id 9896 +0s ... 0s
#1 checking url part for id 14368 +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 Wed, 07 Jun 2023 13:55:12 +0200 +0.001s ... 0.001s
#4 composed specs +0.023s ... 0.024s
#5 did output specs +0s ... 0.024s
#6 getting avg benchmarks for device 9896 +0.012s ... 0.036s
#7 got single benchmarks 9896 +0.01s ... 0.046s
#8 getting avg benchmarks for device 14368 +0.002s ... 0.048s
#9 got single benchmarks 14368 +0.007s ... 0.055s
#10 got avg benchmarks for devices +0s ... 0.055s
#11 min, max, avg, median took s +0.126s ... 0.181s