all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Antoine R. Dumont (@ardumont)" <ardumont@softwareheritage.org>
Cc: guix-devel@gnu.org
Subject: Re: File search
Date: Sun, 11 Dec 2022 11:22:54 +0100	[thread overview]
Message-ID: <87v8mi2q9t.fsf@gnu.org> (raw)
In-Reply-To: <87pmcsriwu.fsf@gmail.com> (Antoine R. Dumont's message of "Fri,  09 Dec 2022 11:05:53 +0100")

Hi!

"Antoine R. Dumont (@ardumont)" <ardumont@softwareheritage.org> skribis:

> |-----------+-------------+----------+----------|
> | Iteration | Host System | Time (s) | Packages |
> |-----------+-------------+----------+----------|
> | 1st       | Debian      |   121.88 |      284 |
> |           | Guix System |   413.55 |      749 |
> |-----------+-------------+----------+----------|
> | 2nd       | Debian      |      1.3 |      101 |
> |           | Guix System |    11.54 |      354 |
> |-----------+-------------+----------+----------|

Ah, that’s a significant difference.

I guess we can keep both methods: the exhaustive one that goes over all
packages, and the quick one.  Then we can have a switch to select the
method.

Typically, we may want to use the expensive one on the build farm to
publish a full database, while on user’s machines we may want to default
to the cheaper one.

>> Oh, and progress bars too.
>
> I'm a bit unsettled on this. Hopefully it was mostly a joke ;)

It wasn’t.  :-)

In the manifest case, we get ‘all-profiles’ is almost instantaneous, so
we immediately known the number of manifests we’ll be working on.

In the package case, the number of packages is known ahead.

The (guix progress) module provides helpers.

But anyway, that’s more like icing on the cake, we can leave that for
later.

Thanks,
Ludo’.


  parent reply	other threads:[~2022-12-11 10:23 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 17:58 File search antoine.romain.dumont
2022-12-02 18:22 ` Antoine R. Dumont (@ardumont)
2022-12-03 18:19   ` Ludovic Courtès
2022-12-04 16:35     ` Antoine R. Dumont (@ardumont)
2022-12-06 10:01       ` Ludovic Courtès
2022-12-06 12:59         ` zimoun
2022-12-06 18:27         ` (
2022-12-08 15:41           ` Ludovic Courtès
2022-12-09 10:05         ` Antoine R. Dumont (@ardumont)
2022-12-09 18:05           ` zimoun
2022-12-11 10:22           ` Ludovic Courtès [this message]
2022-12-15 17:03             ` Antoine R. Dumont (@ardumont)
2022-12-19 21:25               ` Ludovic Courtès
2022-12-19 22:44                 ` zimoun
2022-12-20 11:13                 ` Antoine R. Dumont (@ardumont)
  -- strict thread matches above, loose matches on Subject: below --
2022-01-21  9:03 Ludovic Courtès
2022-01-21 10:35 ` Mathieu Othacehe
2022-01-22  0:35   ` Ludovic Courtès
2022-01-21 19:00 ` Vagrant Cascadian
2022-01-22  0:37   ` Ludovic Courtès
2022-01-22  2:53     ` Maxim Cournoyer
2022-01-25 11:15       ` Ludovic Courtès
2022-01-25 11:20         ` Oliver Propst
2022-01-25 11:22           ` Oliver Propst
2022-01-22  4:46 ` raingloom
2022-01-22  7:55   ` Ricardo Wurmus
2022-01-24 15:48     ` Ludovic Courtès
2022-01-24 17:03       ` Ricardo Wurmus
2022-02-02 16:14         ` Maxim Cournoyer
2022-02-05 11:15           ` Ludovic Courtès
2022-01-25 23:45 ` Ryan Prior
2022-02-05 11:18   ` Ludovic Courtès
2022-02-06 13:27 ` André A. Gomes

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=87v8mi2q9t.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=ardumont@softwareheritage.org \
    --cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.