Re: git-svn mergeinfo support performance problem
- From
- Andrew Myrick <amyrick@gmail.com>
- Date
- Dec 20, 2009, 00:39 UTC
- Message-ID
- <6b2f9b1d0912191639m3c4feeaaw72a52adb674ad744@mail.gmail.com>
- In-Reply-To
- <4B2D6FB0.6080103@gmail.com>
On Sat, Dec 19, 2009 at 4:28 PM, Johan 't Hart <johanthart@gmail.com> wrote:
Show 10 quoted lines
> Andrew Myrick schreef: >> >> I've been testing git-svn v1.6.6-rc3's mergeinfo support on a large >> svn repository (60,000+ revisions, 20+ GiB) that uses a very >> branch-heavy integration model in which every change gets its own >> branch before being committed to trunk. As a result of the model, >> there are currently over 1000 lines in the svn:mergeinfo property on >> trunk. > > Just wondering: Isnt this workflow stalling svn itself alot too?
Nope, svn seems to handle it fine.
Show 5 quoted lines
> And also: > Do you delete the branches after you reintegrated them? If so, I think its > safe for you to cleanup the svn mergeinfo once in a while. That should not > affect 'svn log -g' because the mergeinfo is still there in older revisions. > I think svn benefits from this too...
We do not delete branches after they've been reintegrated. Bug fix and feature branches can get reintegrated into multiple release branches, so it's not obvious when a branch can be deleted. There's already enough process overhead that it's simpler just to leave all of the branches around. Since this doesn't seem to affect svn's performance, we haven't really worried about it.
-Andrew