On Mon, Dec 10, 2012 at 1:54 PM, Jan Engelhardt <jengelh@inai.de> wrote:
On Mon, Dec 10, 2012 at 12:38 PM, Jan Engelhardt <jengelh@inai.de> wrote:
I tell you, make -l is awesome magic; it sort of autobalances your obs process tree between "1 worker using 24 gccs" and "24 workers using 1 gcc each" roughly. Needless to say, this requires that one always looks at the *host's* load, so make -l out of the box is useless for VM builds ATM.
Cool magic, I didn't know it.
So that's why ARM builds take forever?
ARM is emulated. (At least I can't spot any arm-type workers in build.opensuse.org/monitor)
Exactly, so make -l only sees VM load, not host load. For all others, it should see host load since last I checked OBS worked on a chroot, not a VM for "native" builds.
build.opensuse.org uses Xen/KVM.
If that's so, then I'd suggest -j WORKER_JOBS -l WORKER_INSTANCES (and setting WORKER_JOBS = # of cores per VM) Also, I've noticed dedicating one core to the dom0 improves I/O considerably. Though it's not practicable on dual-cores, when there are many cores it does help. If not done, there's no real parallelism of CPU vs I/O, because virtualization and task switching on the dom0 get in the way. Especially true for network I/O, which seems to be a weak spot in some Xen deployments on not-overly-new hardware with paravirtualization. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org