unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: guix package --search slow ?
Date: Wed, 15 May 2019 15:34:39 +0200	[thread overview]
Message-ID: <87r28zu9hs.fsf@gnu.org> (raw)
In-Reply-To: <CAJ3okZ1cTPXfvhQ0D=qFGVJecMB-GchZ20eJZMZ56L37Do2XAQ@mail.gmail.com> (zimoun's message of "Wed, 15 May 2019 11:54:30 +0200")

Hi zimoun,

zimoun <zimon.toutoune@gmail.com> skribis:

> Your machine is probably faster than mine ;-)

For the record, commit 94aeec0aef03ab44e41bfc3e77c3b623cb3d607c, shortly
before 1.0, make ‘guix search’ faster (as in less CPU usage.)

>  $ time guix package --search=numpy
> real    0m7.353s
> user    0m1.256s
> sys     0m0.136s
>
> $  time guix package --search=conduit
> real    0m0.728s
> user    0m0.764s
> sys     0m0.044s
>
> compared to Debian `aptitude` for example:
>
>  $ time aptitude search numpy
> real    0m3.513s
> user    0m0.692s
> sys     0m0.092s
>
>  $ time aptitude search conduit
> real    0m0.622s
> user    0m0.540s
> sys     0m0.048s

The cold-cache timings are worse for Guix, which ends up doing a lot of
I/O to traverse all these .scm files; APT only has to go through a
couple of files I guess.

The warm-cache timings are comparable though, which I think is good.
:-)

We could probably improve the cold-cache timings by adding synopses and
descriptions to the package cache that ‘guix pull’ builds in
~/.config/guix/current/lib/guix/package.cache, but that would also make
that cache bigger.  Not sure if it’s worth it.

Thanks,
Ludo’.

  parent reply	other threads:[~2019-05-15 13:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-14 17:19 guix package --search slow ? zimoun
2019-05-14 20:17 ` Ricardo Wurmus
2019-05-15  9:54   ` zimoun
2019-05-15 11:35     ` Ricardo Wurmus
2019-05-15 13:34     ` Ludovic Courtès [this message]
2019-05-15 13:43       ` Pierre Neidhardt
2019-05-16 15:13         ` Ludovic Courtès
2019-05-15 13:48       ` Jonathan Brielmaier
2019-05-15 14:08         ` Pierre Neidhardt
2019-05-15 14:50           ` zimoun
2019-05-15 15:11             ` Pierre Neidhardt
2019-05-15 14:31         ` zimoun
2019-05-15 14:23       ` zimoun
2019-05-15 18:32       ` zimoun
2019-05-15 20:30       ` Giovanni Biscuolo
2019-05-15  2:22 ` Meiyo Peng
2019-05-15  9:59   ` zimoun
2019-05-15 14:08   ` zimoun

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=87r28zu9hs.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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).