3 ms·
What's the performance impact for nested virtualization in general? I'd think this would be adding multiple layers of MMU overhead.
by api 8mo ago
What's the performance impact for nested virtualization in general? I'd think this would be adding multiple layers of MMU overhead.
- dwattttt 8mo agoFrom memory, the virtualisation operations themselves aren't nested. The VM instructions interact with the external virtualisation hardware, so it's more of a cooperative situation, e.g. a guest can create & manage virtualisation structures that are run alongside it. I don't know if this applies to the specific nested virtualisation AWS are providing though.
- otterley 8mo agoAs a practical matter, anywhere from 5-15%.
- blibble 8mo agodepends on the workload and how they've done it pure CPU should be essentially unaffected, if they're not emulating the MMU/page tables in software the difference in IO ranges from barely measurable to absolutely horrible, depending on their implementation traps/vmexits have another layer to pass through (and back)