Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of email.workbench@gmail.com
 designates 209.85.161.44 as permitted sender)
MIME-Version: 1.0
Sender: email.workbench@gmail.com
In-Reply-To: 
 <CAPExE9=ydjOc=112+h9yEj_kgBghqwu-0JeK4tQ-JR4A6Ao7RQ@mail.gmail.com>
References: 
 <CAPExE9k9Vs9HA5J4_qR_isQEtSp90U_GJVO-XJV-gnorkw460g@mail.gmail.com>
	<CAPExE9=ydjOc=112+h9yEj_kgBghqwu-0JeK4tQ-JR4A6Ao7RQ@mail.gmail.com>
Date: Tue, 5 Jul 2011 03:32:41 -0400
Message-ID: 
 <CAPExE9nsat2SGe10qT1dL3s8NVjXJH1HWwkkGd4FoJkK+N2R4A@mail.gmail.com>
Subject: Re: few doubts
From: Zdravko Gligic <zgligic@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1

oh, i hate gmail, as it seems to react to certain key combinations ...

Focus - It seems that CouchDB has been purposely designed with "single
mindedness in mind".  The approach seems to be that it can be most
efficient if its various functions and its various tasks do small
amounts of work in the most efficient way possible.  So, it would seem
that writes keep on writing to the end of file, instead of flipping
through it and trying to over-write and update in place existing docs.
 Again, in order to be as efficient as it can be with those writes, it
foregoes updating the views (the same way that an RDBMS would update
all of the related indices as part of its record update) and leaves it
for another process which will concentrate on doing just that.  So, it
seems that "context switching" or not having to do much of such
switching is where it gets lots of it processing efficiency.

Again, I am most anxious to see how my noob understandings check out
with technical realities.  ;)

HTH,
teslan