On 17.02.2011 21:43, Mark Phippard wrote:
> On Thu, Feb 17, 2011 at 3:35 PM, Ivan Zhakov <ivan_at_visualsvn.com> wrote:
>
>> I'm looking to memory usage issues in svn update/export/switch in
>> ra_serf. And I come to question: what is the rationale of using
>> 'skelta' update REPORT mode, and then sending many GETs/PROPFINDs
>> instead of using send-all='true' mode and receiving all deltas and
>> properties in one response? Does it make sense to implement
>> send-all='true' mode in ra_serf?
> Wasn't the original idea that the GET requests could be served by a
> HTTP proxy in front of the server? And also that running multiple
> GET's at once would be faster?
>
> I do not think the proxy has turned out to be a reality and it does
> not work with SSL, so maybe not a bad idea.
Issuing multiple GETs in parallel will amortize the request latency over
the number of parallel requests, and will typically also make better use
of available bandwidth -- all of which makes ra_serf faster than
ra_neon. Going back to a single huge request will not only throw away
those benefits, it will also likely change the way a
checkout/update/etc. can be resumed after a connection error.
-- Brane
Received on 2011-02-18 00:26:08 CET