Mailing-List: contact commits-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Mon, 19 Apr 2010 22:49:26 -0000
Message-ID: <20100419224926.7509.69742@eos.apache.org>
Subject: 
 =?utf-8?q?=5BCouchdb_Wiki=5D_Trivial_Update_of_=22Frequently=5Fasked=5Fqu?=
 =?utf-8?q?estions=22_by_fana?=

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for c=
hange notification.

The "Frequently_asked_questions" page has been changed by fana.
The comment on this change is: typo.
http://wiki.apache.org/couchdb/Frequently_asked_questions?action=3Ddiff&rev=
1=3D26&rev2=3D27

--------------------------------------------------

  =

  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-co=
lumn) index on a table in an RDBMS that just performs a quick look-up. So t=
his 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 tha=
t) allowing any number of parallel readers as well as serialized writes. Wi=
th replication, you can even set up multiple machines for a horizontal scal=
e-out and data partitioning (in the future) will let you cope with huge vol=
umes 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).
+ The major advantage of the architecture is, however, that it is designed =
for high traffic. No locking occurs in the storage module (MVCC and all tha=
t) allowing any number of parallel readers as well as serialized writes. Wi=
th replication, you can even set up multiple machines for a horizontal scal=
e-out and data partitioning (in the future) will let you cope with huge vol=
umes 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).
  =

  =

 =20