1 |
On Tue, Mar 24, 2015 at 03:01:14PM -0400, Fernando Rodriguez wrote |
2 |
|
3 |
> Let me know if you have any luck with pump mode, I didn't. IIRC it sort of |
4 |
> worked but most compiles fell back to compiling locally so it's was actually |
5 |
> slower. |
6 |
|
7 |
It appears to be working. It took a couple of tries to get it going. |
8 |
That final required change was to /etc/distcc/hosts on the client. |
9 |
Apparently the required syntax for pump mode is like so |
10 |
|
11 |
192.168.123.251,cpp,lzo |
12 |
|
13 |
where 192.168.123.251 is the host. "cpp" enables pump mode, and "lzo" |
14 |
(for compression) is also required. I originally ran... |
15 |
|
16 |
emerge -pv --changed-use --deep --update @world |
17 |
|
18 |
...on the client. Things looked OK, so I ran |
19 |
|
20 |
pump emerge --changed-use --deep --update @world |
21 |
|
22 |
...and let er rip. I don't have X fully functional on the client yet, |
23 |
so I switched to another text console on the client and ran (as per |
24 |
documentation). |
25 |
|
26 |
DISTCC_DIR="" distccmon-text 5 |
27 |
|
28 |
It spits out the occasional linefeed but no text. However, looking at |
29 |
tty12 on the *HOST* I see a bunch of stuff like... |
30 |
|
31 |
Mar 25 00:51:39 d531 distccd[22479]: (dcc_job_summary) client: 192.168.123.253:38023 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:1548ms i686-pc-linux-gnu-gcc /var/tmp/portage/dev-libs/glib-2.42.2/work/glib-2.42.2/gio/gdbusintrospection.c |
32 |
Mar 25 00:51:42 d531 distccd[22456]: (dcc_job_summary) client: 192.168.123.253:38024 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:930ms i686-pc-linux-gnu-gcc /var/tmp/portage/dev-libs/glib-2.42.2/work/glib-2.42.2/gio/gdbusmethodinvocation.c |
33 |
Mar 25 00:51:45 d531 distccd[22510]: (dcc_job_summary) client: 192.168.123.253:38025 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:1092ms i686-pc-linux-gnu-gcc /var/tmp/portage/dev-libs/glib-2.42.2/work/glib-2.42.2/gio/gdbusserver.c |
34 |
Mar 25 00:51:47 d531 distccd[22463]: (dcc_job_summary) client: 192.168.123.253:38026 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:299ms i686-pc-linux-gnu-gcc /var/tmp/portage/dev-libs/glib-2.42.2/work/glib-2.42.2/gio/gdbusinterface.c |
35 |
|
36 |
So it appears that the host is doing the grunt work. Text is scrolling |
37 |
on the screen of the Atom client just like a local build, but it's going |
38 |
by faster than I remember in the past. |
39 |
|
40 |
> The rest of this post (or parts) may not apply if you do get it |
41 |
> working. |
42 |
> |
43 |
> I've also found that I get better performance without the -l N on |
44 |
> MAKEPOTS and specifying the number of cores per host as follows: |
45 |
> |
46 |
> distcc-config --set-hosts "192.168.123.251/4" |
47 |
> |
48 |
> It may not matter if you got only one host. Also change the -j N flag |
49 |
> accordingly. You'll need to do some testing to find the right number, |
50 |
> I've find that between 4 to 8 cores per physical core works best (for |
51 |
> some reason varies between hosts). Just look for the right number, |
52 |
> you'll know when you see the CPU usage maxing on the hosts during a |
53 |
> parallel build. Keep in mind that most makefiles don't do a lot of |
54 |
> parallel compiling so you need to use the monitor utility to check |
55 |
> during a busy time. |
56 |
|
57 |
I already see an improvement. I have plenty of room for more speedup. |
58 |
CPU load on the host is stable around 0.30, so it's not being overloaded |
59 |
at all. |
60 |
|
61 |
> Also if you're using wireless and you can connect via ethernet do |
62 |
> that because you will see a LOT of traffic. |
63 |
|
64 |
I avoid wireless at home... |
65 |
|
66 |
1) I live in a condominium, and all channels are very busy from my |
67 |
neighbours. |
68 |
|
69 |
2) The ancient Atom netbook only does 802.11 "a" and "b" so it's not |
70 |
that fast. |
71 |
|
72 |
-- |
73 |
Walter Dnes <waltdnes@××××××××.org> |
74 |
I don't run "desktop environments"; I run useful applications |