Hacker News new | ask | show | jobs
by mrb 3397 days ago
"Ryzen 7 is definitely not suited for gamers"

The underperformance in gaming was tracked down to software issues according to AMD. Namely:

- bugs in the Windows process scheduler (scheduling 2 threads on same core, and moving threads across CPU complexes which loses all L3 cache data since each CCX has its own cache)

- buggy BIOS accidentally disabling Boost or the High Performance mode (feature that lets the processor adjust voltage and clock every 1 ms instead of every 40 ms.)

- games containing Intel-optimized code

More info: http://wccftech.com/amd-ryzen-launch-aftermath-gaming-perfor...

Furthermore hardcore gamers usually play at 1440p or higher in which case there is no difference in perf between Intel or AMD, as demonstrated by the many benchmarks (because the GPU is always the bottleneck at such high resolutions.)

2 comments

"Hardcore" is different from "hardware enthusiast".

Hardcore is that guy who plays Call of Duty 24x7 on his Xbox 360 and mediocre 720p television. You can't deny the determination or enthusiasm. Hardware's irrelevant.

> bugs in the Windows process scheduler

Blaming windows is just a desperate excuse from AMD to justify its lack of performances. Don't be tricked by that.

It's possible -and rather common- that there are motherboard issues on the first generation of MB, which again, is not a a valid excuse but a bad thing that desperately needs fixing from AMD and a sign that it's still in testing phase.

Were you around for when bulldozer came out? There were huge problems with Windows task scheduling that were later fixed with updates.
Or when Intel HT first appeared. Or when Intel HT reappeared. Or when the first dual core appeared. Every time Windows needed updates to perform properly; Linux also needed patches to adjust scheduling for Zen and also received patches in many other instances.

This is nothing new or outstanding at all.

The scheduling decisions of Windows are not unknowable. It was entirely AMD's call to make a CPU that was effectively hyperthreaded but to still mark the cores as fully independent.
A Google searches indicates that this is not accurate.