How does compaction time change as my database grows? Is it a function of database size, number of changes since the last compaction, or something else? Also, if I have many write instances all replicating their changes to a master read instance, how will this impact compaction? Does replication effectively perform bulk updates to reduce the need for compaction on the read node? If not, does the same warning about compacting a database under high write load also apply to a database under high replication load (with changes being replicated to this database)?
I'm designing a system that, other than being write-heavy, is a great fit for CouchDB. I'm just trying to figure out how to architect things to work best with lots of writes. Thanks, Ben
