| 1 |
On Fri, Sep 11, 2015 at 6:08 PM, walt <w41ter@×××××.com> wrote: |
| 2 |
> My very old and slow ~amd64 machine took 3 hours and 45-minutes to |
| 3 |
> compile systemd-226 today. I was curious to know why it was taking so |
| 4 |
> long to finish, so I used 'top' to see what was happening. |
| 5 |
> |
| 6 |
> Turns out that two instances of 'sh' were each using 15-30% of CPU for |
| 7 |
> a total of 30-60% (the machine has two CPUs). cc1 never even showed up |
| 8 |
> in 'top' although the compiler was obviously compiling code because the |
| 9 |
> build did eventually finish. |
| 10 |
> |
| 11 |
> I tried the same on a faster 4-core machine and I could see much the |
| 12 |
> same thing happening during the systemd build. |
| 13 |
> |
| 14 |
> Can anyone else reproduce what I'm seeing? Is this 'normal'? |
| 15 |
|
| 16 |
I have noticed that systemd takes quite a long time to build, but I |
| 17 |
have never spent any effort looking into exactly why. |
| 18 |
|
| 19 |
If you figure anything out, please file a bug with your findings. |
Archives