3 ms·
This bug doesn’t magically chop all CPU performance down by almost a third.
by BoorishBears 9y ago
This bug doesn’t magically chop all CPU performance down by almost a third.
- cjbprime 9y agoWhat does it do, then? That is approximately what the mitigation patch does, according to early averages of perf changes.
- Choco31415 9y agoPerformance is chopped 5-30%, with newer CPU's with PCID being affected less significantly. [0] BoorishBears is possibly pointing out that 30% is a worst case. [0]: https://www.phoronix.com/scan.php?page=article&item=linux-415-x86pti&num=1 https://www.phoronix.com/scan.php?page=article&item=linux-41...
- BoorishBears 9y agoThis combined with what the other comment mentions, it's a range from 5%-30% with 30% being a worst case the average user does not encounter. This is an issue, but laypeople are overblowing the effect on their everyday computing.
- BuckRogers 9y agoWhat about gaming performance? Once everything is patched[0], that is. I know no one knows, but it'll be interesting to see Intel's last remaining advantage (clock frequency) mitigated somewhat by all of this. [0]https://gist.github.com/woachk/2f86755260f2fee1baf71c90cd6533e9 https://gist.github.com/woachk/2f86755260f2fee1baf71c90cd653...
- colanderman 9y agoSyscall-heavy workloads are affected to a much greater degree than CPU-heavy workloads. (This is a direct consequence of the fact that the workaround involves a per-syscall overhead.)
- Waterluvian 9y agoYes. Which is why I'm saying "up to 30%"