couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kowsik <>
Subject Compaction...
Date Fri, 23 Jan 2009 17:04:32 GMT
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,

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.



View raw message