4 ms·

Thanks, that seems to align with what I understand too. But I thought perhaps a new architecture, like M1, would have had some additional protection.

• touisteur 6y ago
  But can you drop it on a per-thread or per-process or per-core basis? That would help, no?
  • ddworken 6y ago
    What do you mean by "drop it"? I guess I could imagine that a CPU would allow a specific process to disable speculative execution. That could be an interesting feature though I'm skeptical that any real world applications would actually want to opt-out of speculative execution if it makes things drastically.
    • touisteur 6y ago
      Well that depends on your app/system and how much processing you do for each network interaction. Some of us don't really receive and parse 67 billions HTTP requests + json every second. If tail/mean latency increases a bit, well, let's concentrate HW to avoid network interactions, at least network reception/parsing. Just looking for a way out of the mitigation quagmire for people/orgs who own the hardware and don't share it with external untrusted parties. For all the talk about threat modelling, everyone seems to think we all want -20% perf on the whole machine, while only one or two processes do net I/O...