On Wed, Aug 14, 2013 at 1:13 PM, <dlellis_at_rockwellcollins.com> wrote:
> This is a case of trying to improve performance on externals by only
> updating externals that have changed. Without connection caching,
> performing an external update over a WAN is a test of patience. For us, our
> repo is accessed over a WAN. Its not an issue for non-"file externals".
> For example, a WC of 1000 file externals will take over 15 minutes to update
> with zero changes but the same WC with no file externals (1000 normal files)
> takes 30 seconds tops. Keep in mind, no actual file revisions are being
> downloaded, just checked.
I guess I've always thought file externals were a bad idea (not giving
svn a place for metatdata, at least when it was organized in the same
tree) and avoided using them - so I've never seen that problem. And,
I've always thought organizing by directories was a good thing, along
with pinning the revs for externals which sounds horrible with 1000 of
them referencing individual files.
Received on 2013-08-14 20:28:45 CEST