On Tue, Apr 06, 2021 at 03:43:29PM +0800, Rico Lin wrote:
The job `devstack-platform-arm64` runs around 2.22 hrs to 3.04 hrs, which is near two times slower than on x86 environment. It's not a solid number as the performance might change a lot with different cloud environments and different hardware.
I guess right now we only have one ARM64 cloud so it won't vary that much :) But we're working on it ... I'd like to use this for nodepool / diskimage-builder end-to-end testing, where we bring up a devstack cloud, build images with dib, upload them to the devstack cloud with nodepool and boot them. But I found that there was no nested virtualisation and the binary translation mode was impractically slow; like I walked away for almost an hour and the serial console was putting out a letter every few seconds like a teletype from 1977 :) $ qemu-system-aarch64 -M virt -m 2048 -drive if=none,file=./test.qcow2,media=disk,id=hd0 -device virtio-blk-device,drive=hd0 -net none -pflash flash0.img -pflash flash1.img Maybe I have something wrong there? I couldn't find a lot of info on how to boot. I expected slow, but not that slow. Is binary translation practical? Is booting cirros images, etc. big part of this much longer runtime? -i