[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Sparse checkout feature (immediate children, including folders) of 1.5 is too slow imho

From: Bryce Ready <bready_at_byu.net>
Date: Thu, 10 Jul 2008 18:07:59 -0600

I recently updated to version 1.5.0 of tortoisesvn:
TortoiseSVN 1.5.0, Build 13316 - 32 Bit , 2008/06/21 07:55:29
Subversion 1.5.0,
apr 1.2.12
apr-utils 1.2.12
berkeley db 4.4.20
neon 0.28.2
OpenSSL 0.9.8g 19 Oct 2007
zlib 1.2.3

I was excited to use the new 'Sparse Checkout' feature. I administer a repo
that is big with lots of data, and I want to be able to check out a few
toplevel directories and then 'drill down' to fix things only where I need
them.

When I did a fresh checkout of the root of my repository, using the
"immediate children, including folders" option, it took the better part of
an hour. Judging by the number of bytes transferred, my entire repository
was downloaded and discarded, except for the immediate children of the
repository root. Every time I want to "drill down," I have to essentially
do the same thing over again (at least for the first few steps). Since my
repo structure doesn't branch out widely for several steps, it will take me
several hours to construct my desired sparse working copy.

It would sure be nice if I could quickly (as in downloading only the actual
folders that will end up in the working copy) perform this kind of
checkout. Is there a reason why the entire fully recursive file tree must
be downloaded and most of it discarded (if that is indeed what is
happening)?

-Bryce
Received on 2008-07-11 07:13:36 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.