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

List:       gentoo-user
Subject:    Re: [gentoo-user] Re: long compiles
From:       Alan McKinnon <alan.mckinnon () gmail ! com>
Date:       2023-09-12 18:59:41
Message-ID: CAEdtorZfw823tzNc2Pi2m5=yFfCTJT2mgkiitd0FG3Zu2+-Y9g () mail ! gmail ! com
[Download RAW message or body]

On Tue, Sep 12, 2023 at 11:19 AM Nikos Chantziaras <realnc@gmail.com> wrote:

> On 11/09/2023 22:19, 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.
>
> What's your CPU and how much RAM? Even on my older system I had (an
> 4-core i5 2500K) libreoffice took like 2 hours or so to build.
>
>
> > What other packages have huge build times?
>
> IIRC, dev-qt/qtwebengine is one of the heaviest when it comes to build
> times.
>
> Anyway, a nice way to cut down on build times is to build on tmpfs. To
> do that however with heavy packages like that, I had to upgrade to 32GB
> RAM. There was a large price drop in the memory market a couple months
> ago, so I snatched a 32GB DDR4 3600 kit (2x16GB) for like 80€. So now
> with plenty of RAM, I configured a 14GB tmpfs in /var/tmp/portage. I
> never hit swap when emerging.
>

That's not an option for me, this is a corporate laptop with 16G RAM and a
case I may not open :-)
I'm not interested in a remote build host or distcc either

But anyways, this is not really about how to deal with long compiles, I was
asking what current packages take a long time after a 5 year absence.

The answer is what it was always - browsers and libreoffice. I do recall
icu being a bit of a beast back then


Alan




-- 
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 11:19 AM Nikos Chantziaras &lt;<a \
href="mailto:realnc@gmail.com">realnc@gmail.com</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 11/09/2023 22:19, Alan McKinnon wrote:<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>
What&#39;s your CPU and how much RAM? Even on my older system I had (an <br>
4-core i5 2500K) libreoffice took like 2 hours or so to build.<br>
<br>
<br>
&gt; What other packages have huge build times?<br>
<br>
IIRC, dev-qt/qtwebengine is one of the heaviest when it comes to build <br>
times.<br>
<br>
Anyway, a nice way to cut down on build times is to build on tmpfs. To <br>
do that however with heavy packages like that, I had to upgrade to 32GB <br>
RAM. There was a large price drop in the memory market a couple months <br>
ago, so I snatched a 32GB DDR4 3600 kit (2x16GB) for like 80€. So now <br>
with plenty of RAM, I configured a 14GB tmpfs in /var/tmp/portage. I <br>
never hit swap when emerging.<br></blockquote><div><br></div><div>That&#39;s not an \
option for me, this is a corporate laptop with 16G RAM and a case I may not open \
:-)</div><div>I&#39;m not interested in a remote build host or distcc \
either<br></div><div><br></div><div>But anyways, this is not really about how to deal \
with long compiles, I was asking what current packages take a long time after a 5 \
year absence.</div><div><br></div><div>The answer is what it was always - browsers \
and libreoffice. I do recall icu being a bit of a beast back \
then</div><div><br></div><div><br></div><div>Alan<br></div><div><br></div><div>  \
<br></div></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]