One useful enhancement is coming to help here. The db info will include a data_size value, which is the size of the real data inside the data (basically the size the file will be after you compact it). You can use this value to decide when to compact, rather than doing it on a fixed time schedule. For example, you could scan all databases on an hourly basis but only initiate compaction for databases and views that would shrink by more than 50%.
B. On 11 July 2011 07:41, Randall Leeds <[email protected]> wrote: > CouchDB can *only* reclaim space with compaction. > > There is a setting for limit how much information on old revs is stored: > See comments here: > http://stackoverflow.com/questions/2108144/limit-the-number-of-revisions-in-couchdb > > Setting this value too low might create problems with replication. > You still need to compact to free the space. > > On Sun, Jul 10, 2011 at 23:26, Panop Suvaphrom <[email protected]> wrote: >> >> Thanks, Can we also have an option by limiting some revision on view and >> data so >> the data are not growing such huge. >> >> >> -----Original Message----- >> From: kowsik [mailto:[email protected]] >> Sent: Monday, July 11, 2011 1:18 PM >> To: [email protected] >> Subject: Re: Regard to Space >> >> On Sun, Jul 10, 2011 at 11:05 PM, Panop Suvaphrom <[email protected]> >> wrote: >>> Hi Guys, >>> >>> I know couchdb have provide api to clean a space upon view and >>> compact db. >>> Do you know how other ways around by always let's couchdb to >>> clean up its old data. >> >> From what I know, auto compaction is just around the horizon. Until then, >> you have to do the dirty work yourself. >> >> K. >> --- >> http://blitz.io >> http://twitter.com/pcapr >> http://blog.mudynamics.com >> >
