From: "Ludovic Courtès" <ludo@gnu.org>
To: 53156@debbugs.gnu.org, Efraim Flashner <efraim@flashner.co.il>
Subject: bug#53156: GUIX_DAEMON_SOCKET with ssh doesn't cache connections
Date: Fri, 20 May 2022 23:36:22 +0200 [thread overview]
Message-ID: <87a6bbx4x5.fsf@gnu.org> (raw)
In-Reply-To: <87k0f7y0nz.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 10 Jan 2022 18:13:04 +0100")
Hi Efraim,
Should we close this one?
https://issues.guix.gnu.org/53156
Ludo’.
Ludovic Courtès <ludo@gnu.org> skribis:
> Hi Efraim,
>
> Efraim Flashner <efraim@flashner.co.il> skribis:
>
>> I'm experimenting some more with GUIX_DAEMON_SOCKET, and while when
>> using guix offload I see a socket a /run/user/1000/destination/socket,
>
> What’s this file?
>
>> there's nothing similar when using
>> GUIX_DAEMON_SOCKET=ssh://other-machine. Depending on the machine in
>> question it can take several minutes before a build is started,
>
> That’s because the daemon RPC protocol is suboptimal in that it makes
> lots of round trips, and round trips are very costly over SSH due to
> higher latency.
>
> Eventually we’ll need to adjust/change the protocol, but there’s no
> short-term solution.
>
> (For connections over TCP, ‘open-inet-socket’ in (guix store) uses
> TCP_NODELAY to make this acceptable. There’s #:nodelay #t in (guix
> ssh), but that doesn’t much as much of a difference.)
>
>> and I'm having a hard time maintaining the connection until the end of
>> a longer build like gccgo.
>
> Is it that the SSH server eventually drop the connection?
>
> HTH,
> Ludo’.
prev parent reply other threads:[~2022-05-20 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 9:44 bug#53156: GUIX_DAEMON_SOCKET with ssh doesn't cache connections Efraim Flashner
2022-01-10 17:13 ` Ludovic Courtès
2022-05-20 21:36 ` 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
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=87a6bbx4x5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=53156@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/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).