From: ludo@gnu.org (Ludovic Courtès)
To: guix-devel <guix-devel@gnu.org>
Subject: Re: wip-http-pipelining needs testing!
Date: Mon, 23 Mar 2015 22:34:14 +0100 [thread overview]
Message-ID: <87fv8vv1nt.fsf@gnu.org> (raw)
In-Reply-To: <87h9w4hnxi.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 05 Jan 2015 23:18:01 +0100")
ludo@gnu.org (Ludovic Courtès) skribis:
> Last month Mark installed Nginx on Hydra, with proper caching of
> narinfos. After some debugging, wip-http-pipelining is now in a good
> shape: it has performance comparable to what we currently have, *and*
> it’s single-threaded and shows a progress report while downloading
> substitute info (aka. narinfo.)
>
> I would very much welcome further testing. To do that, you need to run
> the daemon like this (you need both the daemon and ‘guix
> substitute-binary’ from this branch):
>
> sudo ./pre-inst-env guix-daemon --build-users-group=whatever ...
>
> Then just use the guix commands with substitutes enabled. To force an
> update, you can clear the local cache with a command like:
>
> sudo rm -rf /var/guix/substitute-binary/cache/
>
> See <http://lists.gnu.org/archive/html/guix-devel/2014-06/msg00069.html>
> for some background.
I realized that the best way to get more testing was to merge it, so
here goes. :-)
Hopefully it’ll make our lives brighter. The worst that can happen is
for things to become slower. This may be the case when you stumble upon
narinfos not yet cached by nginx on hydra.gnu.org. Fortunately, as the
number of users tends to infinity, the probability of querying a
non-cached narinfo tends to zero.
Feedback and bug reports welcome!
Ludo’.
prev parent reply other threads:[~2015-03-23 21:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 22:18 wip-http-pipelining needs testing! Ludovic Courtès
2015-03-23 21:34 ` Ludovic Courtès [this message]
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=87fv8vv1nt.fsf@gnu.org \
--to=ludo@gnu.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.