The AMD Athlon 300U is a mobile entry level dual core SoC that was announced in January 2019. It combines two Zen cores (with SMT / Hyperthreading so running 4 threads) clocked at 2.4 - 3.3 GHz with a Radeon RX Vega 3 graphics card with 3 CUs (192 Shaders) clocked at up to 1000 MHz. Specified at 15 Watt TDP, the SoC is intended for thin mid-range laptops. It is quite similar to the AMD Ryzen 3 3200U (2.6 - 3.5 GHz).
Compared to the Picasso APUs of the Ryzen 3000 series, the Athlon 300U is still based on the first generation of the 2000 series. Only the PRO variant is based on the new Zen+ microarchitecture that should lead to a 3% IPS (performance per clock) improvement.
The integrated dual-channel memory controller supports up to DDR4-2400 memory. As the features of the Picasso APUs are the same compared to the Raven Ridge predecessors, we point to our Raven Ridge launch article.
In contrast to the faster quad-core Picasso APUs, the Athlon 300U only supports 3 instead of 4 displays in total.
Performance wise, the Athlon 300 should be slightly slower than the Ryzen 3 2200U (2.5 - 3.4 GHz Dual Core with SMT).
The AMD Ryzen 5 2500U is a mobile APU for thin and light laptops that was announced in October 2017. It includes four Zen cores clocked at 2 to 3.6 GHz and offers 4 MB L3-Cache. The integrated graphics card is called Radeon RX Vega 8 and offers 8 CUs (512 Shaders) clocked at up to 1100 MHz. The TDP is configurable between 12 and 25 Watt (15 Watt nominal). More information on Raven Ridge can be found in our launch article.
- 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 31. 05:27:45
#0 checking url part for id 11201 +0s ... 0s
#1 checking url part for id 9310 +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 Sun, 28 May 2023 13:55:04 +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 11201 +0.002s ... 0.025s
#7 got single benchmarks 11201 +0.01s ... 0.035s
#8 getting avg benchmarks for device 9310 +0.012s ... 0.047s
#9 got single benchmarks 9310 +0.057s ... 0.104s
#10 got avg benchmarks for devices +0s ... 0.104s
#11 min, max, avg, median took s +0.25s ... 0.354s