Capacity limit on Branches and Tags in SVN
Hi, I'm looking to migrate an existing repository from CVS into SVN and I've been trying to find concrete examples of capacity limits. Our workflow is to create private branches for bug fixing, feature development, RC testing etc so we end up with a lot of branches and tags over time - CVS is now struggling to support this (time taken to branch is hours). I've seen plenty examples given about the physical size or number of commits supported in an SVN repository, but nothing about the number of branches and tags that can be supported. Basically I'm concerned about performance degradation over time if we continue to create many branches. The numbers I'm talking about are around 2000 branches and 3000 tags, increasing by about 500 per year. Any information or links appreciated. Thanks, Colin Fraser This electronic message (whether email or facsimile) and any attachments may contain confidential, proprietary or non-public information. This information is intended solely for the designated recipient(s). If you are not the designated recipient, please notify the sender immediately and destroy this message. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this message are the personal views of the author. Level Four Software Ltd. Registered in Scotland No. SC157659. Registered office: Level Four House, Pitreavie Court, Dunfermline, Fife, KY11 8UU, UK Level Four Americas LLC. 5960 Fairview Road, Suite 400, Charlotte, NC 28210, USA Level Four (Middle East). Al Thuraya Tower 1, 2nd Floor - Office 209, Dubai Internet City, P.O. Box 500274, Dubai, U.A.E
Re: Capacity limit on Branches and Tags in SVN
On Tue, Mar 1, 2011 at 08:51, Colin Fraser wrote: > Hi, > > I'm looking to migrate an existing repository from CVS into SVN and I've been > trying to find concrete examples of capacity limits. > > Our workflow is to create private branches for bug fixing, feature > development, RC testing etc so we end up with a lot of branches and tags over > time - CVS is now struggling to support this (time taken to branch is hours). > I've seen plenty examples given about the physical size or number of commits > supported in an SVN repository, but nothing about the number of branches and > tags that can be supported. > > Basically I'm concerned about performance degradation over time if we > continue to create many branches. The numbers I'm talking about are around > 2000 branches and 3000 tags, increasing by about 500 per year. > > Any information or links appreciated. Subversion branches and tags are just specially-named copies (you don't even have to call them "branch" or "tag" if you don't want). Copies in Subversion are cheap - each will take maybe 1KB of space. See http://svnbook.red-bean.com/nightly/en/svn.branchmerge.using.html You shouldn't have the same trouble in SVN as you've had in CVS.
Re: Capacity limit on Branches and Tags in SVN
On Mar 1, 2011, at 07:51, Colin Fraser wrote: > I'm looking to migrate an existing repository from CVS into SVN and I've been > trying to find concrete examples of capacity limits. > > Our workflow is to create private branches for bug fixing, feature > development, RC testing etc so we end up with a lot of branches and tags over > time - CVS is now struggling to support this (time taken to branch is hours). > I've seen plenty examples given about the physical size or number of commits > supported in an SVN repository, but nothing about the number of branches and > tags that can be supported. > > Basically I'm concerned about performance degradation over time if we > continue to create many branches. The numbers I'm talking about are around > 2000 branches and 3000 tags, increasing by about 500 per year. > > Any information or links appreciated. There isn't a limit, that I'm aware of. One of the big advances in Subversion over CVS is that branches and tags are implemented differently, and can be created in a short more or less constant amount of time. In Subversion, they're just ordinary directories, and there's not a limit on that in Subversion either. http://svnbook.red-bean.com/nightly/en/svn.forcvs.branches-and-tags.html Having thousands of items in a directory that's checked out can be problematic, but you presumably won't be trying to check out all thousands of your tags at once, so that should be fine. I also wouldn't expect you to keep those thousands of branches around. Feature branches -- those created for bugfixes or new features -- should be deleted (or at least moved to an archive directory) once they've been merged into the trunk. http://svnbook.red-bean.com/nightly/en/svn.branchmerge.commonpatterns.html#svn.branchmerge.commonpatterns.feature
Re: Trying to revive a repo
Kevin Korb gmail.com> writes: > > We were backing up the repository files, but not a dump. We lost the server and we're trying to restore the repo.When we run a svnadmin verify, we get this back...* Verified revision 0.svnadmin: Revision file lacks trailing newlineThe files are all there, and they seem fine... How do we go about trying to fix the issue?Any ideas would be greatly appreciated!Thanks. I suspect this error may have bunch of root causes. In my repository, the db corruption was a revs/* file full of binary zero ... in other words never written with data. My server is v1.6.11. The broken revision was identified by the svnadmin dump command which stopped at the failure. The server had continued to accept updates after the failure. The failure was probably caused by a file system full on the svn machine. >From the svnnotify mail box, I was able to determine the the failed update which turned out to be the build system creating a version tag. For this description assume: 1000 revision in the db 950 last valid revision dumped by svnadmin 951 corrupted revision So I created a new respository NEW and primed it with the first part of ORIG. svnadmin create /resos/NEW svnadmin dump /repos/ORIG -r0:950 | svnadmin load /repos/NEW from a client machine ... svn copy -r950 svn+ssh://svn/repos/NEW/trunk \ svn+ssh://svn/repos/NEW/tags/build-950 then on the svn server: svnadmin dump /repos/ORIG -r952:1000 --incremental | svnadmin load /repos/NEW
Commit failure /error
Hello Guys. One of my users encountered the following error during a huge commit ... The commits fails after commit of around 70-80 MB or even 40+ MB .. Subsequent commit progresses and fails again at a different point .. Error: Commit failed (details follow): Error: At least one property change failed; repository is unchanged Error: Server sent unexpected return value (502 Proxy Error ( The specified network Error: name is no longer available. )) in response to PROPPATCH request for '/' The user is in Germany and the server is a virtual server in India What is causing this error? Mit freundlichen Grüßen / Best regards Maxmelbin Neson RBEI/EMT5
