> Ah, that is in the batch mode, and you were syaing that "one request > with multiple objects" would allow multiple object-info requests to > be hanled efficiently even in non-batch mode. If that was what you > were talking about, I think that does make sense. Thanks. Correct, also I think you mean "buffer" mode rather than "batch" mode. On Thu, May 5, 2022 at 12:09 PM Junio C Hamano <gitster@xxxxxxxxx> wrote: > > Junio C Hamano <gitster@xxxxxxxxx> writes: > > > I would have expected to see something like > > > > start batch > > request 1 > > request 2 > > ... > > request 2000 > > flush batch > > > > during which the other side patiently listens to our requests. They > > (meaning the local process that reads the above and talks to a > > remote as needed) can coalesce the requests of the same kind > > (e.g. going to the same remote) while buffering and optimize their > > operation without having the caller of them to worry about it that > > way, no? > > Ah, that is in the batch mode, and you were syaing that "one request > with multiple objects" would allow multiple object-info requests to > be hanled efficiently even in non-batch mode. If that was what you > were talking about, I think that does make sense. Thanks. >
