The AMD Ryzen 7 2700U is a mobile SoC that was announced in October 2017. It combines four Zen cores (8 threads) clocked at 2.2 - 3.8 GHz with a Radeon RX Vega 10 graphics card with 10 CUs (640 Shaders) clocked at up to 1300 MHz. The TDP can be configured by the laptop manufacturer between 12 to 25 Watt (15 Watt nominal) and therefore the APU is also suited for thin and light laptops. The integrated dual-channel memory controller supports up to DDR4-2400 memory. More information on Raven Ridge can be found in our launch article.
The performance of the Zen CPU cores should be better than a high end Kaby-Lake-Refresh Quad-Core CPU (e.g. the Core i7-8650U) according to AMD. Therefore, the Ryzen 7 2700U is suited for all applications.
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).
- 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.28
log 06. 02:58:45
#0 ran 0s before starting gpusingle class +0s ... 0s
#1 checking url part for id 9314 +0s ... 0s
#2 checking url part for id 11201 +0s ... 0s
#3 redirected to Ajax server, took 1728176325s time from redirect:0 +0s ... 0s
#4 did not recreate cache, as it is less than 5 days old! Created at Fri, 04 Oct 2024 05:16:25 +0200 +0s ... 0s
#5 composed specs +0.005s ... 0.005s
#6 did output specs +0s ... 0.005s
#7 getting avg benchmarks for device 9314 +0.004s ... 0.009s
#8 got single benchmarks 9314 +0.013s ... 0.023s
#9 getting avg benchmarks for device 11201 +0.001s ... 0.023s
#10 got single benchmarks 11201 +0.004s ... 0.028s
#11 got avg benchmarks for devices +0s ... 0.028s
#12 min, max, avg, median took s +0.044s ... 0.072s