On 08/17/2016 12:55 AM, Ryan Schmidt wrote: [snip] > He means avoid the 2x disk use by using "svn export" instead of "svn > checkout". > [snip] > > Of course Subversion only transfers changes. >
Situation summary for the many-large-files scenario. Something like: svn checkout svn://URL/ProjX/branches/profile1 ~/test cd ~/test svn switch ^/branches/profile2 the branch switch will work nicely with a many-large-files data-set, only transferring the files necessary to complete the new profile. But the storage requirements for the working copy (~/test) is twice (2x) the size of the checked-out data-set. Alternatively, using the export method: svn export svn://URL/ProjX/branches/profile1 ~/test will transfer all of the files of profile1 and the storage requirements for the working copy is only (1x) the size of the data-set. But switching between branches is not available in the export method. To switch branches (using the export method): svn export svn://URL/ProjX/branches/profile1 ~/test (transfers all files in profile1) rm -rf ~/test svn export svn://URL/ProjX/branches/profile2 ~/test (transfers all files in profile2) So basically, the checkout method will require twice (2x) the data-set size of storage space for a working copy but there would be significantly less network load during many of the branch switches. The export method pretty much has the opposite storage/network trade-off.
