On 1/25/06, Dan White <dwhite@clubmom.com> wrote:
> Unfortunately we didn't consider how repository
> level versioning (which has no benefit in this application) would
> inflate the db size. Some 6000 files, each only a few kb in size, and
> 62000 revisions later, our /db/revs dir is about 19gb in size and
> growing almost 1gb daily. We never have multiple file commits.
This is the first I've heard about reposity level versioning inflating
the db size. Could you elaborate? If I did my math right (19,000,000kb
/ 62,000 revs) you're averaging about 300kb per commit. That does seem
high to me. And if you're growing at 1gb/day that means you're getting
roughly 3,300 commits/day. That sound about right?
I'm wondering if you could remove older revisions periodically? The
dump file outputs revisions in date order but I don't know if you
could chop off, say, the first 20,000 revisions without borking the
resulting loaded repo or not. Anyone tried this?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 27 23:30:15 2006