> From: Edward Ned Harvey [mailto:s...@nedharvey.com] > > I may take exception: > http://subversion.apache.org/docs/release-notes/1.6.html > says "There is no need to dump and reload your repositories. Subversion > 1.6 > can read repositories created by earlier versions." > > I'll solidify my findings, and I expect that I'll recommend updating > the > above message. But that's just a prediction for now. ;-)
Yup. That's 100% confirmed now. As long as the repo was created with 1.5.x, the problem exists, even if the subsequent operations are using 1.6.12 for both client and server (or client and file:///). To test this, I made a copy of our production repo. Using 1.6.12, I did this: "mkdir newrepo; svnadmin create newrepo ; svnadmin dump oldrepo | svnadmin load newrepo" ... It took several hours to complete, and it was clear that it was spending its time on the same problem revs which are known to take forever. After it was complete, I svn export certain revs of certain directories, which are known to have problems ... Timing the results ... repeating the process for both the 1.5 repo and the 1.6 repo. (Again I repeat, both repos contain the same information, and I'm accessing both repos with a 1.6.12 client. Only difference is that one repo was created with 1.5, and the other was created with 1.6.) In all cases, the svn export from the 1.6 repo requires less than 1sec to complete. In all cases, the svn export from the 1.5 repo requires at least 3 sec (which is acceptable) most often 11sec (which is also acceptable) but occasionally 15min (which is not acceptable.) So I'm going to call this "problem solved." I'll just upgrade all the clients, the server, and the repo. I do want somebody to update the website as mentioned above. It should be recommended but not required, to upgrade repos from 1.5 to 1.6 when you upgrade your executables. For performance reasons. (And other reasons too?)
