Some ballpark figures seen in production-adjacent environments for the running VMA count with this change (based on guests with ~30 vCPUs and one or more disks) are around 30,000 - 70,000 before the patch and roughly 2,000 - 5,000 after the patch, which is an order of magnitude improvement in the average case.
The change in actual memory consumption is negligible, but the drastically lower VMA count in the average case will help against hitting VMA count limits imposed by the kernel. This new caching implementation means that in the future, guests can safely become bigger (in terms of vCPUs, virtual disks, IOThreads, etc.) without needing to change the sysctl. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2168803 Title: QEMU 8.2.2 guests crash by exhausting vm.max_map_count with coroutines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2168803/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
