You are not logged in.

#1 2018-07-13 00:46:53

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,597
Website

Distccd ~2x as slow using a bridge adapter vs simple dhcp

I have been compiling with distcc for years using the same 3-4 slave machines to compile. Within the past 3-4 weeks, I have observed a 2x slow down in compilation times that I am unable to explain.

I did discover that when the master machine is using a bridge adapter (either netctl or systemd-networkd), compilation of the linux kernel takes approx 30 min to complete. If I switch to a simple dhcp (non-bridge) configuration, compilation takes the usual 15-16 min to complete.

* Distcc is serving up jobs and I see corresponding load on the slave machines with either network adapter configuration.
* I don't see any errors/warns in the distcc logs nor in dmesg/journalctl output.
* All nodes are running Arch and are up-to-date. Happy to provide any logs/configuration files.

Last edited by graysky (2018-07-13 00:53:33)


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#2 2018-07-13 14:27:28

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,920

Re: Distccd ~2x as slow using a bridge adapter vs simple dhcp

Does you iptables/nftables setup have a BROUTING chain ?
see https://wiki.archlinux.org/index.php/Ne … dge_itself

If that's not the cause, does creating the bridges manually with iproute2 make a difference for the speed ?


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

Board footer

Powered by FluxBB