[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-user
Subject:    Re: [gentoo-user] long compiles
From:       Alan McKinnon <alan.mckinnon () gmail ! com>
Date:       2023-09-12 8:57:51
Message-ID: CAEdtorYG4WAmWM2aidLiqSxtUnRhv2dY0+zAsZ03k3dT-rUDiA () mail ! gmail ! com
[Download RAW message or body]

On Tue, Sep 12, 2023 at 1:05 AM Ramon Fischer <Ramon_Fischer@hotmail.de>
wrote:

> You may also want to take a look at "distcc", with which you can set up
> compiler farms; this can be even combined with "ccache":
>
>      https://wiki.gentoo.org/wiki/Distcc#With_ccache
>
> -Ramon
>


Hi Ramon,

distcc is way more than I need. I'm not complaining about long compile
times and wanting a solution, I was more curious about which packages these
days take long compared to when I was last here 5/6 years ago

Alan




>
> On 11/09/2023 23:46, Alan McKinnon wrote:
> >
> >
> > On Mon, Sep 11, 2023 at 11:23 PM Michael <confabulate@kintzios.com>
> wrote:
> >
> >     On Monday, 11 September 2023 21:21:47 BST Alan McKinnon wrote:
> >     > On Mon, Sep 11, 2023 at 10:05 PM Neil Bothwick
> >     <neil@digimed.co.uk> wrote:
> >     > > On Mon, 11 Sep 2023 21:19:27 +0200, Alan McKinnon wrote:
> >     > > > chromium has been building since 10:14, it's now 21:16 and
> >     still going
> >     > > > so 9 hours at least on this machine to build a browser -
> >     almost as bad
> >     > > > as openoffice at it's worst (regularly took 12 hours).
> >     Nodejs also took
> >     > > > a while, but I didn't record time.
> >     > >
> >     > > Chromium is definitely the worst, and strangely variable. The
> >     last few
> >     > > compiles have taken between 6 and 14 hours. Since it takes
> >     longer than
> >     > > everything else to build, it is usually compiling on its own,
> >     so parallel
> >     > > emerges aren't a factor.
> >     > >
> >     > > Qtwebengine is also bad, not surprising as it is a cut down
> >     Chromium.
> >     > > Emerging world with --exclude then timing build to coincide
> >     with sleep
> >     > > helps, although I haven't quite reached the age where I need
> >     14 hours of
> >     > > sleep a day.
> >     > >
> >     > >
> >     > > --
> >     > > Neil Bothwick
> >     > >
> >     > > If it isn't broken, I can fix it.
> >     >
> >     > Yup, that jibes with what I see. Oh well, just means that the
> >     need for
> >     > overnight compiles did not go away haha
> >     >
> >     > Thanks to every one else that replied too - everyone said much
> >     the same
> >     > thing so I figured one replay to rule them all was the best way
> >     >
> >     >
> >     > Alan
> >
> >     As the old saying goes, "there ain't no substitute to cubic
> >     inches".  Moar
> >     cores and moar RAM is almost always the solution, but with laptops
> >     and older
> >     PCs in general overnight builds soon become inevitable.
> >     Selectively reducing
> >     jobs and adding swap, or for packages like rust placing
> >     /var/tmp/portage on
> >     the disk becomes necessary.
> >
> >     A solution I use for older/smaller laptops is to build binaries on
> >     a more
> >     powerful PC and emerge these in turn on the weaker PCs.
> >
> >     There's also the option of using bin alternatives where available,
> >     e.g.
> >     google-chrome, firefox-bin, libreoffice-bin.
> >
> >     Finally, there is a small scale project to provide systemd based
> >     binaries as
> >     an alternative to building your own:
> >
> >     https://wiki.gentoo.org/wiki/Experimental_binary_package_host
> >
> >
> > As it turns out this laptop is the most powerful machine I have
> > available, my large collection of previous work laptops are getting
> > older and older.
> >
> > Although, I *could* create a ginormous build host on one of the
> > virtualization clusters at work hahaha :-)
> >
> > That link looks interesting, I'll check it out, thanks!
> >
> >
> > --
> > Alan McKinnon
> > alan dot mckinnon at gmail dot com
>
> --
> GPG public key: 5983 98DA 5F4D A464 38FD CF87 155B E264 13E6 99BF
>
>

-- 
Alan McKinnon
alan dot mckinnon at gmail dot com

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Tue, Sep 12, 2023 at 1:05 AM Ramon Fischer &lt;<a \
href="mailto:Ramon_Fischer@hotmail.de">Ramon_Fischer@hotmail.de</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">You may also want to \
take a look at &quot;distcc&quot;, with which you can set up <br> compiler farms; \
this can be even combined with &quot;ccache&quot;:<br> <br>
         <a href="https://wiki.gentoo.org/wiki/Distcc#With_ccache" rel="noreferrer" \
target="_blank">https://wiki.gentoo.org/wiki/Distcc#With_ccache</a><br> <br>
-Ramon<br></blockquote><div><br></div><div><br></div><div>Hi \
Ramon,</div><div><br></div><div>distcc is way more than I need. I&#39;m not \
complaining about long compile times and wanting a solution, I was more curious about \
which packages these days take long compared to when I was last here 5/6 years \
ago</div><div><br></div><div>Alan</div><div><br></div><div><br></div><div>  \
<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <br>
On 11/09/2023 23:46, Alan McKinnon wrote:<br>
&gt;<br>
&gt;<br>
&gt; On Mon, Sep 11, 2023 at 11:23 PM Michael &lt;<a \
href="mailto:confabulate@kintzios.com" \
target="_blank">confabulate@kintzios.com</a>&gt; wrote:<br> &gt;<br>
&gt;        On Monday, 11 September 2023 21:21:47 BST Alan McKinnon wrote:<br>
&gt;        &gt; On Mon, Sep 11, 2023 at 10:05 PM Neil Bothwick<br>
&gt;        &lt;<a href="mailto:neil@digimed.co.uk" \
target="_blank">neil@digimed.co.uk</a>&gt; wrote:<br> &gt;        &gt; &gt; On Mon, \
11 Sep 2023 21:19:27 +0200, Alan McKinnon wrote:<br> &gt;        &gt; &gt; &gt; \
chromium has been building since 10:14, it&#39;s now 21:16 and<br> &gt;        still \
going<br> &gt;        &gt; &gt; &gt; so 9 hours at least on this machine to build a \
browser -<br> &gt;        almost as bad<br>
&gt;        &gt; &gt; &gt; as openoffice at it&#39;s worst (regularly took 12 \
hours).<br> &gt;        Nodejs also took<br>
&gt;        &gt; &gt; &gt; a while, but I didn&#39;t record time.<br>
&gt;        &gt; &gt;<br>
&gt;        &gt; &gt; Chromium is definitely the worst, and strangely variable. \
The<br> &gt;        last few<br>
&gt;        &gt; &gt; compiles have taken between 6 and 14 hours. Since it takes<br>
&gt;        longer than<br>
&gt;        &gt; &gt; everything else to build, it is usually compiling on its \
own,<br> &gt;        so parallel<br>
&gt;        &gt; &gt; emerges aren&#39;t a factor.<br>
&gt;        &gt; &gt;<br>
&gt;        &gt; &gt; Qtwebengine is also bad, not surprising as it is a cut down<br>
&gt;        Chromium.<br>
&gt;        &gt; &gt; Emerging world with --exclude then timing build to coincide<br>
&gt;        with sleep<br>
&gt;        &gt; &gt; helps, although I haven&#39;t quite reached the age where I \
need<br> &gt;        14 hours of<br>
&gt;        &gt; &gt; sleep a day.<br>
&gt;        &gt; &gt;<br>
&gt;        &gt; &gt;<br>
&gt;        &gt; &gt; --<br>
&gt;        &gt; &gt; Neil Bothwick<br>
&gt;        &gt; &gt;<br>
&gt;        &gt; &gt; If it isn&#39;t broken, I can fix it.<br>
&gt;        &gt;<br>
&gt;        &gt; Yup, that jibes with what I see. Oh well, just means that the<br>
&gt;        need for<br>
&gt;        &gt; overnight compiles did not go away haha<br>
&gt;        &gt;<br>
&gt;        &gt; Thanks to every one else that replied too - everyone said much<br>
&gt;        the same<br>
&gt;        &gt; thing so I figured one replay to rule them all was the best way<br>
&gt;        &gt;<br>
&gt;        &gt;<br>
&gt;        &gt; Alan<br>
&gt;<br>
&gt;        As the old saying goes, &quot;there ain&#39;t no substitute to cubic<br>
&gt;        inches&quot;.   Moar<br>
&gt;        cores and moar RAM is almost always the solution, but with laptops<br>
&gt;        and older<br>
&gt;        PCs in general overnight builds soon become inevitable.<br>
&gt;        Selectively reducing<br>
&gt;        jobs and adding swap, or for packages like rust placing<br>
&gt;        /var/tmp/portage on<br>
&gt;        the disk becomes necessary.<br>
&gt;<br>
&gt;        A solution I use for older/smaller laptops is to build binaries on<br>
&gt;        a more<br>
&gt;        powerful PC and emerge these in turn on the weaker PCs.<br>
&gt;<br>
&gt;        There&#39;s also the option of using bin alternatives where \
available,<br> &gt;        e.g.<br>
&gt;        google-chrome, firefox-bin, libreoffice-bin.<br>
&gt;<br>
&gt;        Finally, there is a small scale project to provide systemd based<br>
&gt;        binaries as<br>
&gt;        an alternative to building your own:<br>
&gt;<br>
&gt;        <a href="https://wiki.gentoo.org/wiki/Experimental_binary_package_host" \
rel="noreferrer" target="_blank">https://wiki.gentoo.org/wiki/Experimental_binary_package_host</a><br>
 &gt;<br>
&gt;<br>
&gt; As it turns out this laptop is the most powerful machine I have <br>
&gt; available, my large collection of previous work laptops are getting <br>
&gt; older and older.<br>
&gt;<br>
&gt; Although, I *could* create a ginormous build host on one of the <br>
&gt; virtualization clusters at work hahaha :-)<br>
&gt;<br>
&gt; That link looks interesting, I&#39;ll check it out, thanks!<br>
&gt;<br>
&gt;<br>
&gt; -- <br>
&gt; Alan McKinnon<br>
&gt; alan dot mckinnon at gmail dot com<br>
<br>
-- <br>
GPG public key: 5983 98DA 5F4D A464 38FD CF87 155B E264 13E6 99BF<br>
<br>
</blockquote></div><br clear="all"><br><span class="gmail_signature_prefix">-- \
</span><br><div dir="ltr" class="gmail_signature">Alan McKinnon<br>alan dot mckinnon \
at gmail dot com</div></div>



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic