Clock speeds are still the most reliable gains to get and I’m a huge fan of Apple increasing them mostly steadily for instance or Arm, with node gains eating them. But like, this is such a 2017 PC gamer argument about clocks? The performance is what we care about. Fatter wider cores with better prediction and broad IPC in integer code but at slightly slower clocks in general are going to be better than slightly less robust ones with more frequency in real code if anything — consumer code is notoriously branchy, sloppy, etc.
I would take an M2 Avalanche Core at 3.5GHz for instance over Lion Cove at 5.1 without hesitation if we wanted to get super technical about who comes out on top in some mass assay of real applications.
I would take an M2 Avalanche Core at 3.5GHz for instance over Lion Cove at 5.1 without hesitation if we wanted to get super technical about who comes out on top in some mass assay of real applications.