Dear Wiki user, You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for change notification.
The following page has been changed by JanLehnardt: http://wiki.apache.org/couchdb/Frequently_asked_questions The comment on the change is: reorder view faq ------------------------------------------------------------------------------ Using an http proxy like nginx, you can load balance GETs across nodes, and direct all POSTs, PUTs and DELETEs to a master node. CouchDB's triggered replication facility can keep multiple read-only servers in sync with a single master server, so by replicating from master -> slaves on a regular basis, you can keep your content up to date. - [[Anchor(how_fast_views)]] - == How Fast are CouchDB Views? == - - It would be quite hard to give out any numbers that make much sense. From the architecture point of view, a view on a table is much like a (multi-column) index on a table in an RDBMS that just performs a quick look-up. So this theoretically should be pretty quick. - - The major advantage of the architecture is, however, that it is designed for high traffic. No locking occurs is the storage module (MVCC and all that) allowing any number of parallel readers as well as serialized writes. With replication, you can even set up multiple machines for a horizontal scale-out and data partitioning (in the future) will let you cope with huge volumes of data. (See [http://jan.prima.de/~jan/plok/archives/72-Some-Context.html slide 13 of Jan Lehnardt's essay] for more on the storage module or the whole post for detailed info in general). - [[Anchor(why_no_mnesia)]] == Why Does CouchDB Not Use Mnesia? == @@ -226, +219 @@ Now you can connect to the remote CouchDB through http://localhost:5984/ + [[Anchor(how_fast_views)]] + == How Fast are CouchDB Views? == + + It would be quite hard to give out any numbers that make much sense. From the architecture point of view, a view on a table is much like a (multi-column) index on a table in an RDBMS that just performs a quick look-up. So this theoretically should be pretty quick. + + The major advantage of the architecture is, however, that it is designed for high traffic. No locking occurs is the storage module (MVCC and all that) allowing any number of parallel readers as well as serialized writes. With replication, you can even set up multiple machines for a horizontal scale-out and data partitioning (in the future) will let you cope with huge volumes of data. (See [http://jan.prima.de/~jan/plok/archives/72-Some-Context.html slide 13 of Jan Lehnardt's essay] for more on the storage module or the whole post for detailed info in general). + + + [[Anchor(slow_view_building)]] == Creating my view index takes ages, WTF? ==
