public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Nuno Silva" <nunojsilva@ist.utl.pt>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Genlop wonky again
Date: Sun, 07 Jan 2024 09:54:37 +0000	[thread overview]
Message-ID: <undsb2$app$1@ciao.gmane.io> (raw)
In-Reply-To: 6020182.lOV4Wx5bFT@cube

On 2024-01-05, Peter Humphrey wrote:

> 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.
>

Is this an off-by-one?

While I'm not acquainted with perl,
https://raw.githubusercontent.com/gentoo-perl/genlop/master/genlop has
this:

"For a better prediction we only consider the last 10 merges", followed
by a max() with the number 9, suggesting zero-based indices that would
need to be incremented for the average, but then

    "$tm_secondi = sum(@merge_times) / $#merge_times;"

(That said, I also wonder if the "slicing off" part needs adjustment
too, can the (zero-based?) length be greater than 9 after it was
shortened to be 9? Or am I misunderstanding the code?)

Summing the three merge times and dividing by two I get, if I've not
messed up my calculations, 68 minutes and 27 seconds, matching your
"Currently merging" output.

-- 
Nuno Silva



      parent reply	other threads:[~2024-01-07  9:53 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
2024-01-06 18:02   ` Peter Humphrey
2024-01-07  9:54 ` Nuno Silva [this message]

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='undsb2$app$1@ciao.gmane.io' \
    --to=nunojsilva@ist.utl.pt \
    --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