1 |
Hi, |
2 |
|
3 |
what's taking so long when emerging packages despite distcc is used? |
4 |
|
5 |
I have disallowed compiling on the local machine (which is the one |
6 |
emerge is running on) through distcc settings because the local machine |
7 |
is relatively slow. Yet I can see some gcc processes running on the |
8 |
local machine, and emerging goes painfully slow. Using distcc doesn't |
9 |
seem to make it any faster, though disabling local compiling seems to |
10 |
help a bit. |
11 |
|
12 |
Some compilations are being run on the remote machine, so distcc does |
13 |
work. The log file on the remote machine shows compilation times of a |
14 |
few milliseconds up to about 1.5 seconds at most. The distcc server |
15 |
would be finished with the emerging within maybe 15 minutes, and the |
16 |
client takes several hours already. |
17 |
|
18 |
Is there something going wrong? Is there a way to speed things up as |
19 |
much as I would expect from using distcc? |