[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 20:21:47
Message-ID: CAEdtorY849m08S4CBsDC7VUOChsDf+G9aU7Q081RuRe08HiQVw () mail ! gmail ! com
[Download RAW message or body]

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
-- 
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 10:05 PM Neil Bothwick &lt;<a \
href="mailto:neil@digimed.co.uk">neil@digimed.co.uk</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">On Mon, 11 Sep 2023 \
21:19:27 +0200, Alan McKinnon wrote:<br> <br>
&gt; chromium has been building since 10:14, it&#39;s now 21:16 and still going<br>
&gt; so 9 hours at least on this machine to build a browser - almost as bad<br>
&gt; as openoffice at it&#39;s worst (regularly took 12 hours). Nodejs also took<br>
&gt; a while, but I didn&#39;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&#39;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&#39;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&#39;t broken, I can fix it.<br>
</blockquote></div><br clear="all"></div><div>Yup, that jibes with what I see. Oh \
well, just means that the need for overnight compiles did not go away \
haha</div><div><br></div><div>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</div><div><br></div><div><br></div><div>Alan<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]