I agree that there's a lot of misunderstanding on clocks - I've been on the other end - evaluation and validation of embedded boards, including V1000 Ryzen SoCs

I agree that there's a lot of misunderstanding on clocks - I've been on the other end - evaluation and validation of embedded boards, including V1000 Ryzen SoCs, but I think I'd disagree somewhat with the characterization of clocks as purely "marketing BS." Back in the day, most CPUs had had a fixed clock, but these days modern Intel and AMD chips simply don't - they all clock opportunistically, which depends on powers, thermals, but also workload (try running an AVX-512 loads for example). How do you characterize "clock" in this context? Base (minimum) and Boost (hard limit, now split to Max Turbo <2C and All Boost MC) seem to be reasonably sensible numbers. Now we can argue semantics all day, but to bring it back around if you're just going to say "top clocks" is what the SoC was designed for at a specific workload/power envelope (In AMD's PB, that'd be PPT, TDC, and EDC) then every laptops will "hit their top clocks with no issues," but I'd say that argument (statement?) is a bit circular/pointless. ;P