News for hackers. Stuff that matters.
Re:MongoDB, Data Durability and Improvements coming in 1.8 by jchrisa on Tuesday January 11, 2011 @01:52AM (#2091188)
I agree we need to improve the interactive query capability of CouchDB.

As far as performance, the key with Couch is to keep the view generation speed faster than the insert rate. So if your users are generating less than about 1000 changes a second, you should be fine on a single server.

More than that and you may need to shard / partition, which can be done in a few different way. The leading option is BigCouch: https://github.com/cloudant/bigcouch

Re:MongoDB, Data Durability and Improvements coming in 1.8 by cdavid on Tuesday January 11, 2011 @04:08AM (#2091419)
Actually, the numbers I get are much lower than that (almost two orders of magnitude), but I suspect it is at least partly due to bad usage of couchdb.

I am actually working on simple benchmarks representative of what we do to see if there is something worth submitting as bug issues.