From: "Ludovic Courtès" <ludo@gnu.org>
To: Jonathan Brielmaier <jonathan.brielmaier@web.de>
Cc: guix-devel@gnu.org
Subject: Re: Make guix-publish's URL identical to cache file name
Date: Fri, 06 Nov 2020 10:51:22 +0100 [thread overview]
Message-ID: <87v9ei24px.fsf@gnu.org> (raw)
In-Reply-To: <4a98c618-2c97-0889-62de-9e3bb5815735@web.de> (Jonathan Brielmaier's message of "Wed, 4 Nov 2020 13:01:04 +0100")
Hi,
Jonathan Brielmaier <jonathan.brielmaier@web.de> skribis:
> I'm running myself a smaller cuirass+publish server and I have
> configured the caching on the nginx side and not with `guix publish`.
This is suboptimal because then your /nar responses lack the
‘Content-Length’ header (‘guix publish’ cannot provide that header when
running without ‘--cache’), which in turn means no progress bar, no
estimate of the amount of data downloaded, etc.
> For me it has a dramatic speed up on my German server reaching from
> Germany. So 2-3MB/s on a cold cache hit versus a hot cache with 15MB/s
> and even more.
‘guix publish --cache’ should bring you the same benefits. I’d still
recommend having nginx in front of it (for HTTPS, etc.), but caching can
be disabled in nginx in that case. That’s what we do on
ci.guix.gnu.org.
Ludo’.
next prev parent reply other threads:[~2020-11-06 9:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 8:46 Make guix-publish's URL identical to cache file name Peng Mei Yu
2020-11-04 12:01 ` Jonathan Brielmaier
2020-11-05 1:55 ` Peng Mei Yu
2020-11-13 12:53 ` zimoun
2020-11-06 9:51 ` Ludovic Courtès [this message]
2020-11-06 9:55 ` Ludovic Courtès
2020-11-07 6:03 ` Ricardo Wurmus
2020-11-08 17:08 ` Ludovic Courtès
2020-12-09 8:29 ` Peng Mei Yu
2020-12-14 9:54 ` Ludovic Courtès
2021-01-11 2:13 ` Peng Mei Yu
2020-11-09 2:59 ` Peng Mei Yu
2020-11-12 20:37 ` Ludovic Courtès
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=87v9ei24px.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=jonathan.brielmaier@web.de \
/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).