unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: guix package --search slow ?
Date: Thu, 16 May 2019 17:13:18 +0200	[thread overview]
Message-ID: <8736leh1pt.fsf@gnu.org> (raw)
In-Reply-To: <87o943ygs6.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Wed, 15 May 2019 15:43:37 +0200")

Pierre Neidhardt <mail@ambrevar.xyz> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> 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.
>
> To be clear, did you mean it might not be worth it because of the size
> it takes on the user's drive or because the increase in size might slow
> down the lookup?

If the cache is bigger, loading it may take a bit more time.

On an SSD, I find the timings to be acceptable now, so I’m also a bit
biased.

Ludo’.

  reply	other threads:[~2019-05-16 15:13 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 [this message]
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=8736leh1pt.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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).