Re: [PATCH v1] convert: add "status=delayed" to filter process protocol
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jan 11, 2017, 20:41 UTC
- Message-ID
- <xmqqo9zdnxc3.fsf@gitster.mtv.corp.google.com>
- In-Reply-To
- <17fa31a5-8689-2766-952b-704f433a5b3a@gmail.com>
Jakub Narębski <jnareb@gmail.com> writes:
Show 8 quoted lines
>> 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.