Another might be to try building from /tmp - there's a significant amount of data being written? vs debug.log
On Thu, 1 Jul 2021 at 14:18, Andrew Cagney <[email protected]> wrote: > Set KVM_LOCALDIR=/tmp/pool ? > > On Thu, 1 Jul 2021 at 09:23, D. Hugh Redelmeier <[email protected]> wrote: > >> I have two similar machines for running tests. >> - ThinkCentre M93p Tiny >> - i5-4570T CPU @ 2.90GHz (Haswell generation) >> - as far as I know, all available firmware updates for security (i.e. >> slowdowns) >> - Fedora 34 (arrived at by many upgrades) >> >> They differ in: >> - the first has a 2.5" HDD and 16G of RAM. >> - the second has a SATA SSD and 8G of RAM >> >> A complete kvm-check took >> - on the first 6:10:46 elapsed time >> - on the second 5:25:39 elapsed time >> >> The first system takes about 14% more time than the second. >> >> I suspect that the majority of the effect was disk speed. >> I would have guessed that disk speed would have mattered more. >> _______________________________________________ >> Swan-dev mailing list >> [email protected] >> https://lists.libreswan.org/mailman/listinfo/swan-dev >> >
_______________________________________________ Swan-dev mailing list [email protected] https://lists.libreswan.org/mailman/listinfo/swan-dev
