Why CouchDB?

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).

Why CouchDB?

Posted Sep 23, 2011 8:03 UTC (Fri) by kragilkragil2 (guest, #76172) [Link]

Yeah, if desktop system really are to make an impact on mobile consumer devices all VM-based programms need to get purged or rewritten. Having slow (starting) VMs isn't going to cut it anymore. User experience is more important than developer experience. Apple knows that.
Ideally JS should be the only allowed VM because ideally it is used in the browser already. I know that is not how things work in say Gnome3 atm, but it is how things should end up.

Why CouchDB?

Why CouchDB?

Why CouchDB?

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier! Saves Data!