Are you using Berkeley DB or FSFS? Have you tried using the opposite
database type? If it's Berkeley DB, does that size include the
transactions logs? These log files can get cleaned up periodically.
While I don't know exactly how svn is using Berkeley DB, I do know
from my own projects that use it transaction logs can get quite big
when there are lots of updates.
On Jan 25, 2006, at 12:41 PM, Dan White wrote:
> We've been using svn and trac for a number of development projects.
> When it came time to build a content management system, we felt that
> with its webdav support and easily implement hooks, svn would be a
> good repository for all of our content. We created a new empty
> repository on the same redhat box that hosts our development
> repositories and trac. 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.
>
> Did we just pick the wrong version control app for our needs? Is
> there
> something we can do to compact the db or decrease the rate at which it
> grows? Does anyone have suggestions for another app that does file
> level versioning and supports webdav and hook scripts?
>
> Thanks,
> Dan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
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:54:17 2006