Quote:
Originally Posted by ResAlien
Reading the first article it made it sound at the end that it was more of an issue for cloud providers right? Or is the big concern the performance slapdown everyone is going to get?
|
Depends on what you do with your machine. Anyone who does kernel and specifically virtual memory intensive activities will be impacted. Reason why cloud providers will be hit hard is virtualization on servers for cloud activities is inherently virtual memory/IO intensive and most servers are Intel based atm because of market share. Also unpatched the bug allows one VM to write to the protected memory of another VM, but patched it would result in an up to 30% performance hit. The security implications are massive if left unpatched.
Quote:
Michael Larabel, the open-source guru behind the Linux-centric Phoronix website, has run a gauntlet of benchmarks using Linux 4.15-rc6, an early release candidate build of the upcoming Linux 4.15 kernel. It includes the new Linux KPTI protections for the Intel CPU kernel flaw. The Core i7-8700K saw a massive performance decrease in FS-Mark 3.3 and Compile Bench, a pair of synthetic I/O benchmarks. PostgreSQL and Redis suffered a loss, but to a far lesser degree. Finally, H.264 video encoding, timed Linux kernel compilation, and FFmpeg video conversion tasks didn’t lose anything.
Your mileage will indeed vary, it seems. Keep in mind that Phoronix’s testing was conducted on a non-final release, and that the Linux and Windows kernels are two very different beasts. More testing will need to be performed to see how the Meltdown patch affects Windows PCs and Macs.
|
Some tasks won't be impacted as much, gaming on Linux and video encoding weren't much anyways. Windows specific tasks including directX gaming is TBD.
https://www.pcworld.com/article/3245...ts-pc-mac.html
Some initial benchmark numbers pre/post patch show 15% performance degradation on a pair of recent Intel processors
