Posted Sep 22, 2011 6:22 UTC (Thu) by tajyrink (subscriber, #2750)
Parent article: Why CouchDB?
I'd wish they'd talk more about performance, and how they plan to address those issues. As an example, before Gwibber switched away from CouchDB it was a pain to use on a modern 2.5GHz laptop, not to mention typical rural Africa computer. It also easily ate 1GB of RAM. Also being based on erlang just by existing it causes several wakeups per second apparently just for polling or some sort of cycles in the erlang VM - no concept of idling it seems.
Note that this is from stupid user's point of view, but the performance in a typical application was simply not acceptable, as are not any wakeups when idle. Ideally I'd use couchdb kind of thing on my mobile phone, but I doubt my 128MB RAM, 400MHz phone would handle the couchdb backend of gwibber (I never tried before Debian updated to newer gwibber).