From: Junio C Hamano <gitster@pobox.com>
To: "Jakub Narębski" <jnareb@gmail.com>
Cc: Lars Schneider <larsxschneider@gmail.com>,
Git mailing list <git@vger.kernel.org>, Eric Wong <e@80x24.org>,
Taylor Blau <ttaylorr@github.com>
Subject: Re: [PATCH v1] convert: add "status=delayed" to filter process protocol
Date: Wed, 11 Jan 2017 12:41:32 -0800 [thread overview]
Message-ID: <xmqqo9zdnxc3.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <17fa31a5-8689-2766-952b-704f433a5b3a@gmail.com> ("Jakub Narębski"'s message of "Wed, 11 Jan 2017 15:53:27 +0100")
Jakub Narębski <jnareb@gmail.com> writes:
>> Yes, this problem happens every day with filters that perform network
>> requests (e.g. GitLFS).
>
> Do I understand it correctly that the expected performance improvement
> thanks to this feature is possible only if there is some amount of
> parallelism and concurrency in the filter? That is, filter can be sending
> one blob to Git while processing other one, or filter can be fetching blobs
> in parallel.
The first-object latency may not be helped, but by allowing
"delayed", the latency to retrieve the second and subsequent objects
can be hidden, I would think.
next prev parent reply other threads:[~2017-01-11 20:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-08 19:17 [PATCH v1] convert: add "status=delayed" to filter process protocol larsxschneider
2017-01-08 20:14 ` Torsten Bögershausen
2017-01-11 9:48 ` Lars Schneider
2017-01-08 20:45 ` Eric Wong
2017-01-11 9:51 ` Lars Schneider
2017-01-08 23:42 ` Junio C Hamano
2017-01-10 22:11 ` Jakub Narębski
2017-01-10 23:33 ` Taylor Blau
2017-01-11 10:20 ` Lars Schneider
2017-01-11 14:53 ` Jakub Narębski
2017-01-11 20:41 ` Junio C Hamano [this message]
2017-01-11 9:43 ` Lars Schneider
2017-01-11 20:45 ` Junio C Hamano
[not found] ` <20170109233816.GA70151@Ida>
2017-01-11 10:13 ` Lars Schneider
2017-01-11 17:59 ` Taylor Blau
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=xmqqo9zdnxc3.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=larsxschneider@gmail.com \
--cc=ttaylorr@github.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 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.