You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 16, 2020. It is now read-only.
We observe notable slowness when actively booting qemu vCPU's are 40x overcommitted to physical CPU's. One of our demos is to launch a tonne of workloads. The OS in the workload is very busy booting for a brief spell at start up, but then quiets down. This is a normal startup pattern. Rather than trying to start 10k vm's in parallel, things run better if you launch in parallel until things are "too busy", then launch more as the first ones are becoming less busy.
This knob would tie to the "some multiple" mentioned in issue #99.
The text was updated successfully, but these errors were encountered:
We observe notable slowness when actively booting qemu vCPU's are 40x overcommitted to physical CPU's. One of our demos is to launch a tonne of workloads. The OS in the workload is very busy booting for a brief spell at start up, but then quiets down. This is a normal startup pattern. Rather than trying to start 10k vm's in parallel, things run better if you launch in parallel until things are "too busy", then launch more as the first ones are becoming less busy.
This knob would tie to the "some multiple" mentioned in issue #99.
The text was updated successfully, but these errors were encountered: