unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: francismb <francismb@email.de>
Cc: 61625@debbugs.gnu.org
Subject: bug#61625: Package download speed calculation, spurious results?
Date: Thu, 23 Feb 2023 14:28:30 +0100	[thread overview]
Message-ID: <87leko7bpd.fsf@gnu.org> (raw)
In-Reply-To: <9f94be69-0e66-06ef-a0c5-dc4665d4888b@email.de> (francismb@email.de's message of "Sun, 19 Feb 2023 12:14:42 +0100")

Hi,

francismb <francismb@email.de> skribis:

>  graphviz-2.49.0  1.2MiB
>                          1.15GiB/s 00:00 [                  ]   5.1%
>  graphviz-2.49.0  1.2MiB
>                           2.2MiB/s 00:01 [##################] 100.0%
>
> substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
>
> I'm not behind a ~ >100MB connection, and it's curious to get 1.15GiB/s
> here, is that somehow the value from some cache? or is a spurious
> calculation? (IMHO nothing that releases the packaging unusable thus low
> priority, just curiosity, is that a bug?)

As you can see, the 1.15GiB/s was printed while Guix had downloaded just
5.1% of 1.2 MiB, meaning 61 KiB.

The time it takes to download 61 KiB is very small, which is why you can
end up with surprising values when dividing that by the time it took.

Notice that the final result of 2.2 MiB/s is probably accurate.

There’s not much to do here, except perhaps not displaying anything
until at a bigger chunk of time has elapsed.

Ludo’.




  reply	other threads:[~2023-02-23 13:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-19 11:14 bug#61625: Package download speed calculation, spurious results? francismb
2023-02-23 13:28 ` Ludovic Courtès [this message]
     [not found]   ` <3c5f80e9-6d3b-ea05-cd81-b26957f4a178@email.de>
2023-03-03  9:46     ` Ludovic Courtès

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87leko7bpd.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=61625@debbugs.gnu.org \
    --cc=francismb@email.de \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).