couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Damien Katz <>
Subject Re: Compaction...
Date Fri, 23 Jan 2009 17:29:57 GMT
That would be my suggestion, once a day during a time when the traffic  
is lower is the best time to do a compaction. And you could monitor  
disk free space and kick off compaction(s) when it gets too low.

Eventually we'll get CouchDB to track how much current data is the  
file vs wasted space, so you can compact only the databases that  
actually need it.


On Jan 23, 2009, at 12:22 PM, Troy Kruthoff wrote:

> We're not at the point of using couchdb in production yet, but I  
> assumed cron+curl would take care of this.
> Troy
> On Jan 23, 2009, at 9:04 AM, kowsik wrote:
>> For the most part, I never have to look at Couch once its running
>> since the index generation, id generation, incremental indexing,
>> document updates all __just__ work. For, since the middle
>> tier is Helma (also Javascript), new views in the source are
>> automatically sync'd directly to couch. I can almost completely  
>> relax,
>> except...compaction.
>> Is it possible to do some kind of automatic compaction, similar to
>> auto growing hash tables based on collisions/density or garbage
>> collection? The best place to do this really is the db itself. With
>> this I never have to worry about file sizes growing indefinitely or
>> having to find the best time to compact the database.
>> This might mean, though, that compaction has higher priority than
>> writes. I guess it's a trade off.
>> Thoughts?
>> K.

View raw message