From: Mike Galbraith <efault@gmx.de>
To: Rolf Eike Beer <eb@emlix.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Junio C Hamano <gitster@pobox.com>
Cc: Git List Mailing <git@vger.kernel.org>,
Tobias Ulmer <tu@emlix.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: data loss when doing ls-remote and piped to command
Date: Sat, 18 Sep 2021 08:33:38 +0200 [thread overview]
Message-ID: <9bd95c0ad91bd490adf2b6e57495411a0f72fe50.camel@gmx.de> (raw)
In-Reply-To: <2722184.bRktqFsmb4@devpool47>
On Fri, 2021-09-17 at 08:59 +0200, Rolf Eike Beer wrote:
>
> What you need is a _fast_ git server. kernel.org or github.com seem to be too
> slow for this if you don't sit somewhere in their datacenter. Use something in
> your local network, a Xeon E5 with lot's of RAM and connected with 1GBit/s
> Ethernet in my case.
Even faster: what's coming across that wire should be a constant (is?),
variable is only delivery/consumption jitter. If there's really really
a pipe problem lurking, you should also be able to trigger by saving
the data once, and just catting it, letting interrupts etc provide
jitter. Which stdout is left of '|' in a script shouldn't matter one
whit to the interpreter/kernel conversation, they're all the same.
That said, if I had a reproducer I was confident pointed to the kernel,
I'd try to bisect.. boring as hell, but highly effective.
-Mike
prev parent reply other threads:[~2021-09-18 6:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 12:43 data loss when doing ls-remote and piped to command Rolf Eike Beer
2021-09-15 18:17 ` Junio C Hamano
2021-09-16 6:38 ` Rolf Eike Beer
2021-09-16 10:12 ` Tobias Ulmer
2021-09-16 12:17 ` Rolf Eike Beer
2021-09-16 15:49 ` Mike Galbraith
2021-09-17 6:38 ` Mike Galbraith
2021-09-16 17:11 ` Linus Torvalds
2021-09-16 20:42 ` Junio C Hamano
2021-09-17 6:59 ` Rolf Eike Beer
2021-09-17 19:13 ` Jeff King
2021-09-17 19:28 ` Linus Torvalds
2021-09-18 6:33 ` Mike Galbraith [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=9bd95c0ad91bd490adf2b6e57495411a0f72fe50.camel@gmx.de \
--to=efault@gmx.de \
--cc=eb@emlix.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tu@emlix.com \
/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.
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 NNTP newsgroup(s).