3 ms·

Breakdown from post: ~8% pipelined SET performance reduction after patch ~15% pipelined GET performance reduction after patch ~29% non-pipelined SET performa

Breakdown from post: ~8% pipelined SET performance reduction after patch ~15% pipelined GET performance reduction after patch ~29% non-pipelined SET performance reduction after patch ~25% non-pipelines GET performance reduction after patch

BonesJustice 9y ago
Note also that the host OS (the one running the hypervisor) was already patched in all cases. These tests only reflect the difference between a patched and unpatched guest OS. The total performance reduction is likely greater.
- O_H_E 9y ago
  Wholly Shit Isn't that enough
- eric_h 9y ago
  Good point - I guess it's more or less impossible to do this test on the public cloud, now (at least on the big three). It'd be fun to set up the hardware and do a full matrix benchmark of patched/unpatched host and patched/unpatched guest.
eric_h 9y ago
And this all seems in line with what the expected slowdown would be. Non-pipelined calls will have more syscalls and therefore a bigger slowdown. Glad antirez took the time to do the benchmarks.