91–100 of 209 posts
Earlier quoted context omitted.
Many applications don't need Spectre or Meltdown mitigations, but they should at least put the test parameters up front and not in the fine print.
Many? Anything running a browser needs it because of js. Anything running connected to the internet at all would be well advised to have them because you can take advantage of the exploits via the network stack. Anything running on a vm has to have them since microcode is set by the hypervisor. So, we're talking about desktops not used to browse the internet, and bare metal servers whose network stacks aren't exposed…
All the javascript engines have implemented spectre and meltdown mitigations.
EDIT: Are the downvotes because people don't believe that the JS mitigations are effective?
And if anyone from AMD is reading this. I'm truelly awaiting AMD's NUC in multiple price ranges of 150-700€, if possible :)! I'm currently building a DIY RPi 4 cluster for microservices/kubernetes setup and would like to replace my DIY home streaming setup. http://www.fanlesstech.com/2019/10/exclusive-amds-nuc-is-com...
They wouldn't have an answer to AMD untill 2021: https://newsroom.intel.com/news/2019-intel-investor-meeting/... Ps. Long AMD, perfect execution the last two years. It's crazy, even their late firmware fixes improve performance as it had bad press for a moment for false benchmarks advertisement ( it was not false so it seems, the firmware was just not ok yet. Not everything is fully ok now, it's the only minor nitpic…
AMD also suffered from Spectre and Meltdown. Admittedly not all the variants of it that have since come out, Intel has done way worse there, but AMD instances _are_ vulnerable if they lack microcode updates and OS patches.
Earlier quoted context omitted.
Can I ask for anyone from AMD to sell a 4 socket, epyc mobo. Im looking for 256 (4*64) core desktop PC.
What will you use that many cores for?
There's algorithms that haven't yet been optimized for GPU parallelization. And there's datasets that require memory access patterns that aren't amenable to GPU.
That said, now I'm curious what a 128-core system would do to memory access. Better hope the algorithms are L2/L3 coherent?
They wouldn't have an answer to AMD untill 2021: https://newsroom.intel.com/news/2019-intel-investor-meeting/... Ps. Long AMD, perfect execution the last two years. It's crazy, even their late firmware fixes improve performance as it had bad press for a moment for false benchmarks advertisement ( it was not false so it seems, the firmware was just not ok yet. Not everything is fully ok now, it's the only minor nitpic…
> In the contrary, Intel has a lot of failures the last 2 years. Spectre, meltdown, ... This isn't bad luck anymore, it's more like bad karma if you are religious. AMD also suffered from Spectre and Meltdown. Admittedly not all the variants of it that have since come out, Intel has done way worse there, but AMD instances _are_ vulnerable if they lack microcode updates and OS patches.
They wouldn't have an answer to AMD untill 2021: https://newsroom.intel.com/news/2019-intel-investor-meeting/... Ps. Long AMD, perfect execution the last two years. It's crazy, even their late firmware fixes improve performance as it had bad press for a moment for false benchmarks advertisement ( it was not false so it seems, the firmware was just not ok yet. Not everything is fully ok now, it's the only minor nitpic…
> In the contrary, Intel has a lot of failures the last 2 years. Spectre, meltdown, ... This isn't bad luck anymore, it's more like bad karma if you are religious. AMD also suffered from Spectre and Meltdown. Admittedly not all the variants of it that have since come out, Intel has done way worse there, but AMD instances _are_ vulnerable if they lack microcode updates and OS patches.
> Presently, 13 Spectre variants and 14 Meltdown variants have been identified. Initially, AMD processors were thought to be immune to Meltdown, though one variant has been successfully demonstrated on AMD systems.
ONE variant. So technically true. But the situation on the Intel side is far worse.
Intel got way too greedy with their optimizations.
Earlier quoted context omitted.
Many applications don't need Spectre or Meltdown mitigations, but they should at least put the test parameters up front and not in the fine print.
Many? Anything running a browser needs it because of js. Anything running connected to the internet at all would be well advised to have them because you can take advantage of the exploits via the network stack. Anything running on a vm has to have them since microcode is set by the hypervisor. So, we're talking about desktops not used to browse the internet, and bare metal servers whose network stacks aren't exposed…
To be fair the context here is HPC. Nobody is installing Chrome on something like IBM's Summit supercomputer. Nor is it running "untrusted" code. It's configured to go as fast as possible, nothing more.
Anyone in cloud hosting or desktop would be insane to not install spectre/meltdown fixes. But in this particular niche of HPC supercomputers it's actually reasonable to not have those mitigations.