Your message dated Fri, 24 Jan 2025 09:48:24 +0100
with message-id <[email protected]>
and subject line Re: autopkgtest-buildvm-ubuntu-cloud does not use SMP
has caused the Debian Bug report #1005802,
regarding autopkgtest-buildvm-ubuntu-cloud does not use SMP
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1005802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005802
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: autopkgtest
Version: 5.19
Severity: wishlist
autopkgtest-buildvm-ubuntu-cloud is quite slow due to QEMU running on a
single core:
qemu-system-x86_64 -m 512 -smp 1
cpus=2 would be a more reasonable default value. This may require
raising the default memory size too.
The command should provide a parameter to set the number of cpu cores to
use.
Best regards
Heinrich
--- End Message ---
--- Begin Message ---
Version: 5.31
On Tue, 15 Feb 2022 Heinrich Schuchardt wrote:
> autopkgtest-buildvm-ubuntu-cloud is quite slow due to QEMU running on a
> single core:
>
> qemu-system-x86_64 -m 512 -smp 1
>
> cpus=2 would be a more reasonable default value. This may require
> raising the default memory size too.
>
> The command should provide a parameter to set the number of cpu cores to
> use.
Done in version 5.31:
---
autopkgtest (5.31) unstable; urgency=medium
[ Mateus Rodrigues de Morais ]
* Add --cpus to buildvm-ubuntu-cloud tool
---
On changing the default: I am not sure I second that. We should stay
aligned with the autopkgtest-virt-qemu default I believe, which is
currently 1 cpu. Also, I ran some quick benchmarks on my amd64
laptop with hyperfine(1), and got this:
Benchmark 1: autopkgtest-buildvm-ubuntu-cloud --cpus 1 --proxy= --release noble
Time (mean ± σ): 60.181 s ± 5.422 s [User: 45.961 s, System: 11.781 s]
Range (min … max): 55.835 s … 68.920 s 10 runs
Benchmark 1: autopkgtest-buildvm-ubuntu-cloud --cpus 2 --proxy= --release noble
Time (mean ± σ): 54.952 s ± 5.063 s [User: 46.707 s, System: 13.962 s]
Range (min … max): 48.916 s … 60.864 s 10 runs
so --cpus=1 is faster, but not terribly faster.
Cheers,
Paride
--- End Message ---
