If those tags don't contain mods you might be able to simply note the directory/revision that were tagged and lose the tags entirely.
Otherwise, rewriting the /tags tree's history such that it is sharded (perhaps by quarter as per elsethread) is a non-lossy, but trickier, option. Trevor Schaffer wrote on Wed, Sep 28, 2011 at 10:08:15 -0600: > Thanks. I was expecting that the back end didn't change much either. I'll > look closer at filtering out the commits we don't care about to try to > minimize the tags that we have. > > -----Original Message----- > From: Daniel Shahaf [mailto:d...@daniel.shahaf.name] > Sent: Wednesday, September 28, 2011 9:35 AM > To: Trevor Schaffer > Cc: users@subversion.apache.org > Subject: Re: revs files growing over time, relatively > > Trevor Schaffer wrote on Wed, Sep 28, 2011 at 07:57:35 -0600: > > If anyone has any idea on what we can do with this, I would appreciate > > it. > > > > In the meantime, I'm going to try to dump+load the repo in the hopes > > that there were some optimizations in svn 1.6 that will help. We've > > had this repo running for nearly 5 years, since svn 1.4. > > > > I will also try out svn 1.7, but I don't know how soon we can get that > > into production. We are relying on Subversion Edge, so it can switch > > when that becomes live. > > The storage of directories in FSFS has not changed recently, I expect > you'll see the same issue in 1.7. > > It seems what you'd like to do is rewrite your history such that > directory sizes (max # of siblings) is small. That sounds doable. > > I'm not sure offhand whether the BDB backend has the same issue with > storing large directories. > >
