incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Zdravko Gligic <zgli...@gmail.com>
Subject Re: Frugal Erlang vs Resources Hungry CouchDB
Date Thu, 30 Jun 2011 02:13:32 GMT
If these three points are more or less correct ...

1) CouchDB keeps appending to the end of the file.  Fine.

2) It needs just as much disk space when doing a compaction.  Is that
extra space equivalent to the original uncompacted or the final
compacted version?

3) Compaction is similar to replication in that original documents'
activities are "replayed" into the newly created DB version.

Then ..

a) What does CouchDB "know" during compaction that it does not know
during the original writes - that would make it that much smarter?

b) Are we strictly talking about reclaiming of space held by older
revs that have been subsequently updated or is some sort of "bulking"
at play?

c) So, what about a cases in which there is next to no updating of
existing docs and do compactions make any difference in such cases ?

d) Is compaction similar to replication and if so then would a
continuous replication result in continuously compacted DB ?

Regards and thanks for replying,
teslan

Mime
View raw message