public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: long compiles
Date: Tue, 12 Sep 2023 12:19:46 +0300	[thread overview]
Message-ID: <udpafi$112f$1@ciao.gmane.io> (raw)
In-Reply-To: <CAEdtorbR26rPuFNLpkab6-2i9-OsPMH5UzbMJjKVZp5VVWr2rw@mail.gmail.com>

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.



  parent reply	other threads:[~2023-09-12  9:19 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11 19:19 [gentoo-user] long compiles Alan McKinnon
2023-09-11 19:31 ` Dale
2023-09-11 19:33   ` Siddhanth Rathod
2023-09-11 19:46   ` Alan McKinnon
2023-09-12 21:08     ` Wol
2023-09-13 11:28       ` Peter Humphrey
2023-09-13 11:50         ` Wols Lists
2023-09-13 12:38           ` Frank Steinmetzger
2023-09-13 12:41           ` Peter Humphrey
2023-09-13 15:14             ` Michael
2023-09-14  9:49               ` Peter Humphrey
2023-09-14 12:24                 ` Michael
2023-09-11 19:42 ` Ramon Fischer
2023-09-11 19:46   ` Ramon Fischer
2023-09-11 20:05 ` Neil Bothwick
2023-09-11 20:21   ` Alan McKinnon
2023-09-11 21:22     ` Michael
2023-09-11 21:46       ` Alan McKinnon
2023-09-11 23:04         ` Ramon Fischer
2023-09-12  8:57           ` Alan McKinnon
2023-09-12 10:14       ` Peter Humphrey
2023-09-12 10:57         ` Jacques Montier
2023-09-12  9:26     ` [gentoo-user] " Nikos Chantziaras
2023-09-12  9:19 ` Nikos Chantziaras [this message]
2023-09-12 19:01   ` Alan McKinnon
2023-09-12 19:30     ` Nuno Silva
2023-09-12 22:11     ` Neil Bothwick
2023-09-13 21:15 ` [gentoo-user] " Kristian Poul Herkild
2023-09-13 21:20   ` [gentoo-user] " Grant Edwards
2023-09-13 21:37     ` Neil Bothwick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='udpafi$112f$1@ciao.gmane.io' \
    --to=realnc@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox