We have a project in our repository that is separate from the trunk. It has existed for about 18 months and has about 500 corrections made for it. All changes in the trunk that have passed this time are successively merged into a branch.
At this point, when we start the switch operation between the two, it takes more than two minutes and seems to stop on some specific files.
For testing, I deleted all information about the merger without any luck.
As an additional test, I created a new trunk branch. Then I combined the differences between the original branch and the trunk and passed them to a new branch.
New and old branches are now identical according to svn utilities.
If I switch between a trunk and a new branch, there are no performance issues.
There seems to be something in the repo that causes this. The only thing I can think of at this stage is that since there is a lot of history in the industry, the system compares each revision.
We use svn 1.6 and work through the file: protocol.
Any ideas?
source
share