As many of you will be aware, hardware vulnerabilities have been discovered in many brands and types of CPUs that were manufactured in the last 20 years, affecting computers across the globe.
Here at CCP, we are in the process of patching and performance testing our infrastructure with the aim of making the impact on game performance and player experience as minimal as possible, so that you guys can continue to enjoy blowing up each other’s internet spaceships.
Security patches for macOS, Window 7/8/10 and Linux are all in the process being rolled out from their operating system vendors (from Microsoft, Apple, and the Linux community) to address the issue. Both latest macOS and Windows 10 have already received updates that resolve the issue, and Windows 7 and 8 will receive updates tomorrow (2018/01/08). For many of our pilots, your systems will have either already received an update, if you’re running Windows 10 or latest macOS, or will be due to receive one tomorrow.
There have been reports of increased CPU usage for machines that are running the new update, ranging from a 5 to a 30% increase in CPU load, so we recommend that you keep an eye on your system’s performance.
Since EVE Online primarily uses your system’s graphics card for most of its workload, we anticipate that the performance impact on the EVE Online client will be minimal, however if you do notice any performance impact, or strange client behavior, feel free to let us know.
You can discuss this news item and give feedback, or let us know about issues in this thread on the EVE Online forums.
Since when is this the case? As far as I can remember back CPU has always been the bottleneck for performance. Since I upgraded my machine from a HD5770/Phenom X4 870 to a RX570/Ryzen 1700X the FPS in big fights are still barely in the double digits in potato mode, and certain CPU cores still go into overdrive to cope with EVE.
The major performance hit is only regarding system calls (and only Intel CPUs). Games naturally do not have a need for many system calls and are thus not going to see any noticeable performance impact.
I can’t wait for the microcode update coming soon™.
However the “issue” will not be “resolved” tomorrow but made more difficult to get attacked. It may take up to a year to “fix” the silicone dies.
Everything until then will only make it difficult to make use of the security issue.
Designing a new CPU architecture takes 3 to 4 years. Then you have to factor in production, etc., etc. Expect this to be fixed in 5 years at the earliest, if it’s ever going to happen. Intel is notorious for sticking their head into the sand until it all just goes away on its own.
Then you have always had better GPUs than CPUs/motherboards? The EVE Client is GPU-bound but is very much affected by memory bus bandwidth, not so much clock speed per se but often in the past the two would go hand in hand.