| 1 |
<wabenbau@×××××.com> writes: |
| 2 |
|
| 3 |
> lee <lee@××××××××.de> wrote: |
| 4 |
> |
| 5 |
>> Hi, |
| 6 |
>> |
| 7 |
>> what's taking so long when emerging packages despite distcc is used? |
| 8 |
>> |
| 9 |
>> I have disallowed compiling on the local machine (which is the one |
| 10 |
>> emerge is running on) through distcc settings because the local |
| 11 |
>> machine is relatively slow. Yet I can see some gcc processes running |
| 12 |
>> on the local machine, and emerging goes painfully slow. Using distcc |
| 13 |
>> doesn't seem to make it any faster, though disabling local compiling |
| 14 |
>> seems to help a bit. |
| 15 |
>> |
| 16 |
>> Some compilations are being run on the remote machine, so distcc does |
| 17 |
>> work. The log file on the remote machine shows compilation times of a |
| 18 |
>> few milliseconds up to about 1.5 seconds at most. The distcc server |
| 19 |
>> would be finished with the emerging within maybe 15 minutes, and the |
| 20 |
>> client takes several hours already. |
| 21 |
>> |
| 22 |
>> Is there something going wrong? Is there a way to speed things up as |
| 23 |
>> much as I would expect from using distcc? |
| 24 |
> |
| 25 |
> You can try pump mode. Preprocessing is then done on the remote server. |
| 26 |
> Depending on your hardware, this could be faster. |
| 27 |
> |
| 28 |
> But read carefully the manpages of pump and distcc before you use it. |
| 29 |
> There are some restrictions you should be aware of. |
| 30 |
|
| 31 |
I followed the instructions on the wiki which suggest to have |
| 32 |
'FEATURES="distcc distcc-pump"' in make.conf and give instructions how |
| 33 |
to set the CPUs. |
| 34 |
|
| 35 |
> You can also try to optimize the number of concurrent compile processes |
| 36 |
> (-j). Watching the load counts of your client and server(s) will help |
| 37 |
> you to find out the best value. |
| 38 |
|
| 39 |
Using -j doesn't really help. The server is pretty much idling --- or |
| 40 |
you could say waiting for stuff to compile --- while the client |
| 41 |
progresses awfully slowly and isn't overloaded with compilation |
| 42 |
processes. If the server would get more load, emerging could be much |
| 43 |
much faster. |
| 44 |
|
| 45 |
Can it be that the client is simply too slow compared to the server to |
| 46 |
give it any significant load? (The client isn't exactly slow; it's slow |
| 47 |
compared to the server.) |
Archives