Mailing-List: contact couchdb-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: couchdb-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID;
  b=0VObdlUksrhX8RBGWJTBXo4S312uYumBlJCschbQ/FySUNHfi9pN8+wr1jrmzfAQklQtMPa2KvCGJEels6xvQ2rlj1QZHM/Gvsuz9t9G8fLzeFoB4FOuEUF6WxBMMjHQa/WfatFAXMT/NFajU5pDVhgz+hvCPRVVNz93j0Pompk=;
References: 
 <0E689907656A4B499E477CBB9A24044707FAF656@sryulwis0comx01.coradiant.com>
Date: Tue, 4 Nov 2008 08:07:59 -0800 (PST)
From: Bradford Winfrey <bradswinfrey@yahoo.com>
Subject: Re: Write performance vs. query performance
To: couchdb-user@incubator.apache.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-182308134-1225814879=:21219"
Message-ID: <482447.21219.qm@web57206.mail.re3.yahoo.com>

--0-182308134-1225814879=:21219
Content-Type: text/plain; charset=us-ascii

Well, the first big plus is that it's non-blocking.  So as people are reading, they won't be hung up while the writes finish.  Having said that things that are being written while someone is reading won't be immediately available in said reads (but will be available for any which take place there after as long as the update=false parameter isn't specified).

As I've used it, I can say that I've been quite pleased with it's responsiveness while many reads and writes are being executed simultaneously.  Keep in mind though that each document upon creation is indexed as it's written, so depending on your views, your mileage may vary.

All, correct me where appropriate if I've mislead this guy...

Brad


________________________________
From: Jonathan Ginter <jonathan.ginter@coradiant.com>
To: couchdb-user@incubator.apache.org
Sent: Friday, October 31, 2008 4:10:03 PM
Subject: Write performance vs. query performance

I am curious about the performance of CouchDB for write-intensive
applications.  Our application typically writes in the tens of millions
of records (in this case, documents) per day.  Would CouchDB be able to
handle that kind of load while still being responsive to queries?  Is it
only a matter of scaling up the deployed hardware to solve that problem?


Thanks.


Jonathan


--0-182308134-1225814879=:21219--