It's less about single-core vs. multi-core, and even then, it's really not about quad-core vs more-cores. My thought pattern through all of this (and maybe I'm

It's less about single-core vs. multi-core, and even then, it's really not about quad-core vs more-cores. My thought pattern through all of this (and maybe I'm completely off base) is that, for instance, having a 4-core part with high single-core performance might be preferable to a gamer/enthusiast (depending on common workloads) than an 18-core part with less single-core performance, and that maybe this is all a reason to consider why the weighting of UserBenchmark's "overall" score changed instead of immediately attaching the change to some anti-AMD bias Maybe my idea that the most common workloads of UserBenchmark users (I don't claim to know their demographics, but I figured one could make assumptions based on the types of individuals that would look up benchmarks in the first place- very common among gamers) would see diminishing returns after, say 4 cores, is wrong- but that was how my thought process was going. And a related point I'll concede (I admit my thinking maybe is just too old-school, biased, too filtered through my own experience and needs updating) is maybe there are more games and programs than I thought that actually take advantage of more than four cores.