Re: merge very slow

Lieven Govaerts wrote:

> If the merge code can be optimized to make less ra calls, sure, that's
> better. But in the case that those 149 merge/update reports are really
> needed, I don't see a reason why we cannot reuse earlier idle
> connections in the ra_serf library. Isn't one of the principles of serf
> to allow maximum number of requests over a minimum number of sockets?

This might seem a little bit off topic now, but may I suggest to enhance
the svn_client_* API so that sessions can be re-used between those calls
too?

>> I've looked to merge.c code and I've shocked: we create many ra
>> sessions when merging. This is source of all slowdowns. And also there
>> is no comments why we doing so. Could someone explain why we creating
>> new sessions instead of reusing?
>>
>
> Did you look at the numbers I got from my test case? Only 7 sessions,
> and all of those were created at the start of the merge. So either you
> misinterpreted the code or my code tracing was incorrect. I don't know
> the merge code well enough to know who's right or wrong.

Yes, and I think my assumption was wrong. I'm now testing in another
direction. I'll report back as soon as I find something.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net