unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Guix Devel <guix-devel@gnu.org>
Subject: Re: guix package --search slow ?
Date: Wed, 15 May 2019 20:32:24 +0200	[thread overview]
Message-ID: <CAJ3okZ3=ETFt-AE=__bbyZ2h2WV6AuxuxQC2uZpOgbT6hkoNLQ@mail.gmail.com> (raw)
In-Reply-To: <87r28zu9hs.fsf@gnu.org>

Hi,

My bad !

On Wed, 15 May 2019 at 15:34, Ludovic Courtès <ludo@gnu.org> wrote:

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

`aptitude search` is not equivalent to `guix package --search` but to
`guix package --list-available`.
The `aptitude` equivalence should be `aptitude search '?term(numpy)'`

And now, Guix is better. ;-)

$ time guix package -s numpy
real    0m7.924s
user    0m1.240s
sys     0m0.144s

$ time guix package -s conduit
real    0m0.758s
user    0m0.796s
sys     0m0.044s

compared to:

$ time aptitude search '?term(numpy)'
real    0m7.393s
user    0m1.556s
sys     0m0.628s

$ time aptitude search '?term(conduit)'
real    0m1.824s
user    0m1.352s
sys     0m0.464s


However, I still think that a SQL caching file containing also
descriptions should improve the searching experience with cold cache.

Thanks! Now I have better understood some internals. :-)

All the best,
simon

  parent reply	other threads:[~2019-05-15 18:32 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
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 [this message]
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='CAJ3okZ3=ETFt-AE=__bbyZ2h2WV6AuxuxQC2uZpOgbT6hkoNLQ@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --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 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).