Re: SVN performance -URGENT
On Thu, Aug 1, 2013 at 10:18 AM, Somashekarappa, Anup (CWM-NR) anup.somashekara...@rbc.com wrote: Hello Bob, Thanks for your response. I tried in the same server where svn is hosted but there also it is taking too much of time I e it is taking 110 mins to checkout the 2200 Mbytes of data(in Windows it took 143 mins). CIFS is a very chatty protocol. May I assume that you're checkout out to a network mounted directory? In this case, you might try checkout out to a locally mounted directory, then simply copying the checkout out directory over to your CIFS mount. It's ugly, but it was much, much faster way back in Subversion 1.4.x days. Also, 2 GBytes over a translatlantic checkout is not really that bad. And remember that Subversion is writing all the files *twice*, once in .svn, and once in the actually checkout out copy, so you're effectively transmitting 2 GB and writing 4 GB. Directories with many thousands of files in one directory are *hell* on most operating systems, especially inefficiently configured network mounts. Check for directories that have tens our hundreds of thousands of files in one directory, and avoid that practice. You might also try splitting up the upstream repository, and using svn:extern to cross reference to other repositories. It can make for much smaller, safer checkouts. I have not tried the command line option.Could you please tell how to do it from windows machine? In windows when the checkout is completed I got a message saying 361 Mbytes(different repository) transferred in 102 mins,but it is showing as 1.13GB when I checked the folder size.Why there is so much of difference . See the contents of the .svn subdirectory, which maintains prisitine copies of all the files. Ideally for 361 Mbytes,the checkout should complete in few mins but it is taking 102 mins. :-( I cannot turn off the anti-virus part and check. If nothing else comes to light, consider keeping a pre-staged checkout in a central directory. Download a clean copy of *that*, and simply do svn update and/or svn switch to switch to the relevant tag or branch. Thanks, Anup
merging and ignoring certain directories
Hi All We have a branch A We svn copy A to feature branch Y Time elapsed We svn merge A to Y continuously Time elapsed We svn copy A to branch B (and decided B would be the trunk) Time elapsed We have been merging B to Y continuously We have been checking in jars to branch Y when making builds on Y. Time elapsed Time to merge back from Y to Trunk B Question 1: We like to ignore the build artifacts in Y when merging back B. How do we do that ? What is the exact command ? Question 2: Would --reintegrate option help in this case ? Question 3: We may not want to delete branch Y after merging to B. Can Y continue development and NOT cause merging issues again when we need to merge from Y to B the 2nd time and onward. Thanks all. Sincerely
svn 1.8 causing locks to be broken on update
I 'm using tortoiseSVN, and noticed that when updating the very root of the repository, locks which I have taken under it become broken. Here is output from cygwin. ---begin-output--- $ svn --version svn, version 1.8.1 (r1503906) compiled Jul 22 2013, 19:58:17 on x86-microsoft-windows Copyright (C) 2013 The Apache Software Foundation. This software consists of contributions made by many people; see the NOTICE file for more information. Subversion is open source software, see http://subversion.apache.org/ The following repository access (RA) modules are available: * ra_svn : Module for accessing a repository using the svn network protocol. - with Cyrus SASL authentication - handles 'svn' scheme * ra_local : Module for accessing a repository on local disk. - handles 'file' scheme * ra_serf : Module for accessing a repository via WebDAV protocol using serf. - handles 'http' scheme - handles 'https' scheme Felipe@FELIPES ~ $ cd ~/SVN/Trunk/Lettus/lbin Felipe@FELIPES ~/SVN/Trunk/Lettus/lbin $ ls backup.cron* Felipe@FELIPES ~/SVN/Trunk/Lettus/lbin $ svn st Felipe@FELIPES ~/SVN/Trunk/Lettus/lbin $ svn lock backup.cron svn: warning: W160035: Path '/Trunk/Lettus/lbin/backup.cron' is already locked by user 'felipe' in filesystem '/u3/SVN_Repository/db' Felipe@FELIPES ~/SVN/Trunk/Lettus/lbin $ svn lock --force backup.cron 'backup.cron' locked by user 'felipe'. Felipe@FELIPES ~/SVN/Trunk/Lettus/lbin $ svn st K backup.cron Felipe@FELIPES ~/SVN/Trunk/Lettus/lbin $ cd ../.. Felipe@FELIPES ~/SVN/Trunk $ svn up Updating '.': ULettus\lbin\create_appsvr_links_5.4.sh Updated to revision 59204. Felipe@FELIPES ~/SVN/Trunk $ svn st K Lettus\lbin\backup.cron ? SystemAdmin\rsync.sh MK SystemAdmin\rsync_transfer.cron.FreshASPNEW MK SystemAdmin\rsync_transfer.cron.FreshBNE Felipe@FELIPES ~/SVN/Trunk $ cd .. Felipe@FELIPES ~/SVN $ svn up Updating '.': BTrunk\SystemAdmin\rsync_transfer.cron.FreshASPNEW BTrunk\SystemAdmin\rsync_transfer.cron.FreshBNE BTrunk\Lettus\lbin\backup.cron ---end-output--- -- felipe