Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of jcorvel@gmail.com designates
 209.85.214.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <OF6CB340B5.C3C6F949-ON88257BC8.006630EE-88257BC8.0068AA48@rockwellcollins.com>
References: 
 <OFF155594E.21E036B5-ON88257BC2.007E8623-88257BC2.007F0B83@rockwellcollins.com>
 <OFACEAFF91.6C153F9C-ON88257BC7.0061F8C6-88257BC7.00642543@rockwellcollins.com>
 <OF0D541C73.2F69F9D2-ON86257BC7.006553D1-86257BC7.0067B4C5@LocalDomain>
 <OFD66E75A7.68AF0CA6-ON88257BC7.00682D53-88257BC7.0068BF0C@rockwellcollins.com>
 <CAOAgVpxRMbT4odtwfnVQaEygOE3+TxpzUP8xfLRz3b1ykS_6Kw@mail.gmail.com>
 <CAOAgVpwoevspt6jPk_f-A=guagiM1jaQm5fsBAEFY+aCO64+Uw@mail.gmail.com>
 <CAOAgVpyOHW5vzGwcnJdQDc02E8j98amAA=cvEKUoz_Jfqm6n3g@mail.gmail.com>
 <37BDE060-8006-43D0-A62E-CEB19DF86B98@ryandesign.com>
 <CAOAgVpw-OQmVV352rApN1hpWrvJbLVaYagoynzLG2NqrDiGL7Q@mail.gmail.com>
 <OFF7E6ED96.EB992F54-ON88257BC8.00577C39-88257BC8.0060F644@rockwellcollins.com>
 <CAOAgVpwi_Gkb9mqSMWr4aOWWNx1bdG+y=wMsoDXeH4-uhX+8JA@mail.gmail.com>
 <OF6CB340B5.C3C6F949-ON88257BC8.006630EE-88257BC8.0068AA48@rockwellcollins.com>
From: Johan Corveleyn <jcorvel@gmail.com>
Date: Thu, 15 Aug 2013 21:38:11 +0200
Message-ID: 
 <CAB84uBV5SVWTgRzxAe0W7V4C5VQ0sbXFdCM2SwJG7XGej5CrWQ@mail.gmail.com>
Subject: Re: How to change paths on an external file without a full update
 --depth infinity?
To: dlellis@rockwellcollins.com
Cc: Les Mikesell <lesmikesell@gmail.com>, Ben Reser <breser@apache.org>,
	Ivan Zhakov <ivan@visualsvn.com>, kmradke <kmradke@rockwellcollins.com>,
	Ryan Schmidt <subversion-2012c@ryandesign.com>,
	"users@subversion.apache.org" <users@subversion.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Aug 15, 2013 at 9:03 PM,  <dlellis@rockwellcollins.com> wrote:
...
> The whole discussion has centered on an attempted work around for the
> connection caching that doesn't currently occur for externals.  If that can
> happen, I think we'd be very content.  We're accepting of some performance
> issues.  There was an XKCD a while ago that talked about how much time a
> task takes, how many times you do it and how much waste is created over a
> year.  It was interesting (even if obvious if you thought about it).  I
> think with connection caching we'd hit the sweet spot and working further
> would result in diminishing returns.  This thread is an attempt a hopefully
> short-term work around this limitation.
>

As you've read in the responses by Ben Reser and Ivan Zhakov earlier
in this thread, the ra-session-reuse (connection caching) is work in
progress. That might take some time before it ends up in a final
release (if it's slated for 1.9, that's at least half a year away).

Have you considered setting up something like "write-through
proxying"[1], where you set up local read-only mirrors of your central
svn repository (which transparently sent through write requests to the
master)? That might significantly reduce latency for those read
operations, and might be good enough to make things workable.

[1] http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html#svn.serverconfig.httpd.extra.writethruproxy

-- 
Johan