public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Pielmeier <billie@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Genlop wonky again
Date: Sat, 06 Jan 2024 16:26:49 +0000	[thread overview]
Message-ID: <5AB35FCF-00F4-4638-A18A-A4461F1A73F4@gentoo.org> (raw)
In-Reply-To: <6020182.lOV4Wx5bFT@cube>

Am 5. Januar 2024 23:51:39 UTC schrieb Peter Humphrey <peter@prh.myzen.co.uk>:
>Hello list,
>
>I've just had some strange output from genlop on my 16-thread i5 box, thus:
>
># genlop -t libreoffice | /bin/grep minute
>       merge time: 37 minutes and 38 seconds.
>       merge time: 52 minutes and 59 seconds.
>       merge time: 46 minutes and 17 seconds.
>
># genlop -c
>
> Currently merging 11 out of 11
>
> * app-office/libreoffice-7.5.9.2
>
>       current merge time: 4 minutes and 3 seconds.
>       ETA: 1 hour, 4 minutes and 24 seconds.
>
>### Then, once the update finished:
>
>#  genlop -t libreoffice | /bin/grep minute
>       merge time: 37 minutes and 38 seconds.
>       merge time: 52 minutes and 59 seconds.
>       merge time: 46 minutes and 17 seconds.
>       merge time: 38 minutes and 40 seconds.
>
>I know genlop is, shall we say, not perfect, but how can it be so grossly 
>wrong as that?
>
>I have this in make.conf, and it hasn't changed since I built the machine:
>
>grep '\-j' /etc/portage/make.conf
>EMERGE_DEFAULT_OPTS="--jobs --load-average=12
>MAKEOPTS="-j12 -l12"
>

There are not by chance binary merges which took less than a minute? That might explain the differences.
What is the output wihout the grep or filtering by merge time instead. 

-- 
Best regards
Daniel


  parent reply	other threads:[~2024-01-06 16:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-05 23:51 [gentoo-user] Genlop wonky again Peter Humphrey
2024-01-06  0:54 ` John Blinka
2024-01-06  8:56   ` Wols Lists
2024-01-06 16:12     ` John Blinka
2024-01-06 16:21       ` Wols Lists
2024-01-06 16:29         ` Jack
2024-01-06 17:46           ` gennaro amelio
2024-01-06 17:59         ` Peter Humphrey
2024-01-06 19:28           ` Wols Lists
2024-01-07  0:52             ` Peter Humphrey
2024-01-07  8:34               ` Wols Lists
2024-01-09  3:35                 ` Peter Humphrey
2024-01-09  5:26                   ` Wols Lists
2024-01-07 10:12               ` Wols Lists
2024-01-06 16:26 ` Daniel Pielmeier [this message]
2024-01-06 18:02   ` Peter Humphrey
2024-01-07  9:54 ` [gentoo-user] " Nuno Silva

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=5AB35FCF-00F4-4638-A18A-A4461F1A73F4@gentoo.org \
    --to=billie@gentoo.org \
    --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