[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-11 21:46:42
Message-ID: CAEdtorZwjs59LnzkxRogdc3_GBm+ZweW6G7r3Ld3DbCHBnfXPw () mail ! gmail ! com
[Download RAW message or body]
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
[Attachment #3 (text/html)]
<div dir="ltr"><div><div dir="ltr"><br></div><br><div class="gmail_quote"><div \
dir="ltr" class="gmail_attr">On Mon, Sep 11, 2023 at 11:23 PM Michael <<a \
href="mailto:confabulate@kintzios.com">confabulate@kintzios.com</a>> \
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">On Monday, 11 \
September 2023 21:21:47 BST Alan McKinnon wrote:<br> > On Mon, Sep 11, 2023 at \
10:05 PM Neil Bothwick <<a href="mailto:neil@digimed.co.uk" \
target="_blank">neil@digimed.co.uk</a>> wrote:<br> > > On Mon, 11 Sep 2023 \
21:19:27 +0200, Alan McKinnon wrote:<br> > > > chromium has been building \
since 10:14, it's now 21:16 and still going<br> > > > so 9 hours at \
least on this machine to build a browser - almost as bad<br> > > > as \
openoffice at it's worst (regularly took 12 hours). Nodejs also took<br> > \
> > a while, but I didn't record time.<br> > > <br>
> > Chromium is definitely the worst, and strangely variable. The last few<br>
> > compiles have taken between 6 and 14 hours. Since it takes longer than<br>
> > everything else to build, it is usually compiling on its own, so \
parallel<br> > > emerges aren't a factor.<br>
> > <br>
> > Qtwebengine is also bad, not surprising as it is a cut down Chromium.<br>
> > Emerging world with --exclude then timing build to coincide with sleep<br>
> > helps, although I haven't quite reached the age where I need 14 hours \
of<br> > > sleep a day.<br>
> > <br>
> > <br>
> > --<br>
> > Neil Bothwick<br>
> > <br>
> > If it isn't broken, I can fix it.<br>
> <br>
> Yup, that jibes with what I see. Oh well, just means that the need for<br>
> overnight compiles did not go away haha<br>
> <br>
> Thanks to every one else that replied too - everyone said much the same<br>
> thing so I figured one replay to rule them all was the best way<br>
> <br>
> <br>
> Alan<br>
<br>
As the old saying goes, "there ain't no substitute to cubic inches". \
Moar <br> cores and moar RAM is almost always the solution, but with laptops and \
older <br> PCs in general overnight builds soon become inevitable. Selectively \
reducing <br> jobs and adding swap, or for packages like rust placing \
/var/tmp/portage on <br> the disk becomes necessary.<br>
<br>
A solution I use for older/smaller laptops is to build binaries on a more <br>
powerful PC and emerge these in turn on the weaker PCs.<br>
<br>
There's also the option of using bin alternatives where available, e.g. <br>
google-chrome, firefox-bin, libreoffice-bin.<br>
<br>
Finally, there is a small scale project to provide systemd based binaries as <br>
an alternative to building your own:<br>
<br>
<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>
</blockquote></div><br clear="all"></div><div>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.</div><div><br></div><div>Although, I *could* create a \
ginormous build host on one of the virtualization clusters at work hahaha \
:-)</div><div><br></div><div>That link looks interesting, I'll check it out, \
thanks!</div><div><br></div><div><br></div><div><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></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic