These are some random operational things I learned about CouchDB. While I realize that my primary use-case (a CouchDB install with currently 230+ million documents) may be oversized for many, these are still things important things to know and to consider. And I would have loved to know of some of these before we grew that large. I hope these findings are useful for others. Compaction CouchDB doesn’t take great care of diskspace — the assumption is that disk is cheap....
Update, 2010-03-04: I just rolled a 0.0.2 release. In case you had 0.0.1 installed, just use pear upgrade-all to get it automatically. This release is trying to fix a random hang while reading documents from the source server. I also opened a repository on Github. --- As some may have guessed from a previous blog post we are currently running a test setup with CouchDB lounge. My current objective is to migrate our 200 million documents to it, and this is where I am essentially stuck this week....
One of our biggest issues with CouchDB is currently the lack of compaction of our database, and by lack of, I don’t mean that CouchDB doesn’t support it, I mean that we are unable to actually run it. Compaction in a nutshell Compaction in a nutshell is pretty cool. As you know, CouchDB is not very space-efficient. For once, CouchDB saves revisions of all documents. Which means, whenever you update a document a new revision is saved....