public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ramon Fischer <Ramon_Fischer@hotmail.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] long compiles
Date: Mon, 11 Sep 2023 21:46:04 +0200	[thread overview]
Message-ID: <AM6PR10MB2440CAC12A09F3876423105FEFF2A@AM6PR10MB2440.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <AM6PR10MB244071F0174C3EE1463C91FAEFF2A@AM6PR10MB2440.EURPRD10.PROD.OUTLOOK.COM>


[-- Attachment #1.1.1: Type: text/plain, Size: 3440 bytes --]

In addition to the reference to "qlop":

     $ qlop ungoogled-chromium | tail
     2022-08-04T19:58:22 >>> www-client/ungoogled-chromium: 9:06:54
     2022-08-05T14:27:44 >>> www-client/ungoogled-chromium: 16:19:06
     2022-08-25T11:45:37 >>> www-client/ungoogled-chromium: 8:01:54
     2022-09-01T10:03:19 >>> www-client/ungoogled-chromium: 15:27:22
     2022-09-06T16:29:49 >>> www-client/ungoogled-chromium: 9:46:16
     2022-09-14T17:48:16 >>> www-client/ungoogled-chromium: 9:30:29
     2022-10-08T03:40:44 >>> www-client/ungoogled-chromium: 1:52:16
     2022-10-21T17:58:43 >>> www-client/ungoogled-chromium: 9:24:55
     2022-12-16T17:47:27 >>> www-client/ungoogled-chromium: 20:56:08
     2023-03-20T14:12:02 <<< www-client/ungoogled-chromium: 2s

Since I am using "ccache", the compilation time is sometimes doubled.

ZzZzZzzz
-Ramon

On 11/09/2023 21:42, Ramon Fischer wrote:
> Hi Alan,
>
> just quick and dirty, I am too tired for formalities. :) The following 
> list contains packages, that may be too big for tmpfs and are most 
> probably very time consuming to compile:
>
>     $ < /etc/portage/package.env/no_tmpfs.conf
>     # custom - 20181121 - rfischer: list packages, which are too big 
> for tmpfs
>     #app-editors/neovim no_tmpfs.conf
>     #app-emulation/qemu-kv no_tmpfs.conf
>     #app-office/libreoffice no_tmpfs.conf
>     #dev-db/mysql no_tmpfs.conf
>     #dev-java/icedtea no_tmpfs.conf
>     #dev-lang/ghc no_tmpfs.conf
>     #dev-lang/ghc no_tmpfs.conf
>     #dev-lang/mono no_tmpfs.conf
>     #dev-lang/rust no_tmpfs.conf
>     #dev-lang/spidermonkey no_tmpfs.conf
>     #dev-libs/libpcre no_tmpfs.conf
>     #dev-qt/qtwebengine no_tmpfs.conf #throttle_make_emerge.conf
>     #mail-client/thunderbird no_tmpfs.conf
>     #media-libs/opencv no_tmpfs.conf
>     #media-libs/opencv no_tmpfs.conf
>     #net-libs/nodejs no_tmpfs.conf
>     #net-misc/openssh no_tmpfs.conf
>     #sci-libs/tensorflow no_tmpfs.conf
>     #sys-apps/iproute2 no_tmpfs.conf
>     #sys-devel/clang no_tmpfs.conf
>     #sys-devel/gcc no_tmpfs.conf
>     #www-client/chromium no_tmpfs.conf #throttle_make_emerge.conf
>     #www-client/firefox no_tmpfs.conf
>     #www-client/ungoogled-chromium no_tmpfs.conf 
> #throttle_make_emerge.conf
>
> See also:
>
> * 
> https://wiki.gentoo.org/wiki/Portage_TMPDIR_on_tmpfs#Considering_tmpfs.27_size
> * 
> https://wiki.gentoo.org/wiki/Q_applets#Extracting_information_from_emerge_logs_.28qlop.29
>
> Sleeps away.
> -Ramon
>
> On 11/09/2023 21:19, Alan McKinnon wrote:
>> After my long time away from Gentoo, I thought perhaps some packages 
>> that always took ages to compile would have improved. I needed to 
>> change to ~amd64 anyway (dumb n00b mistake leaving it at amd64). So 
>> that's what I did and let emerge do it's thing.
>>
>> 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 other packages have huge build times?
>>
>> -- 
>> Alan McKinnon
>> alan dot mckinnon at gmail dot com
>

-- 
GPG public key: 5983 98DA 5F4D A464 38FD CF87 155B E264 13E6 99BF


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 8969 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2023-09-11 19:46 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 [this message]
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
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=AM6PR10MB2440CAC12A09F3876423105FEFF2A@AM6PR10MB2440.EURPRD10.PROD.OUTLOOK.COM \
    --to=ramon_fischer@hotmail.de \
    --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