Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 94103 invoked from network); 19 Apr 2010 07:51:48 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 19 Apr 2010 07:51:48 -0000 Received: (qmail 69731 invoked by uid 500); 19 Apr 2010 07:51:47 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 69404 invoked by uid 500); 19 Apr 2010 07:51:44 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 69393 invoked by uid 99); 19 Apr 2010 07:51:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Apr 2010 07:51:44 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of fredrik.widlund@qbrick.com designates 62.13.40.40 as permitted sender) Received: from [62.13.40.40] (HELO mail.qbrick.com) (62.13.40.40) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Apr 2010 07:51:37 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.qbrick.com (Postfix) with ESMTP id 42685519E2 for ; Mon, 19 Apr 2010 09:51:17 +0200 (CEST) Received: from mail.qbrick.com ([127.0.0.1]) by localhost (mail0.p0.w0.local [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 48855-01-9 for ; Mon, 19 Apr 2010 09:51:16 +0200 (CEST) Received: from exchange0.ad.qbrick.com (exchange0.ad.qbrick.com [10.16.0.4]) by mail.qbrick.com (Postfix) with ESMTP id 76B9F519DE for ; Mon, 19 Apr 2010 09:51:16 +0200 (CEST) Received: from exchange0.ad.qbrick.com ([10.16.0.4]) by exchange0.ad.qbrick.com ([10.16.0.4]) with mapi; Mon, 19 Apr 2010 09:52:45 +0200 From: Fredrik Widlund To: "user@couchdb.apache.org" Content-Class: urn:content-classes:message Date: Mon, 19 Apr 2010 09:52:44 +0200 Subject: RE: Ezra doesn't recommend CouchDB_ Thread-Topic: Ezra doesn't recommend CouchDB_ Thread-Index: AcrfPfkjtrnBmEpYQWmot/EEDteWYAAVsPyA Message-ID: References: <9AFB5212-C996-4FA7-9ACB-6EE228E59223@me.com> In-Reply-To: Accept-Language: sv-SE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: sv-SE, en-US Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Anybody using a replicated setup, with say at least 5-10 nodes or so? If so= can you state an average load in terms of ops/sec and cpu? Kind regards, Fredrik -----Original Message----- From: James Hayton [mailto:theboss@purplebulldog.com] Sent: den 18 april 2010 23:26 To: user@couchdb.apache.org Subject: Re: Ezra doesn't recommend CouchDB I know this guy is a founder of engine yard, but I really question if he knows what he is talking about here. He said Mongo was durable and unless = I am missing something, Mongo openly admits that they trade durability for speed. CouchDB is probably the most durable solution out there I think (I regularly just kill an amazon ec2 instance in the middle of something and never had a problem...), which is something he says he values when he recommends Tokyo, Mongo and Redis. I am really curious why he says he wouldn't even consider using CouchDB. I am using CouchDB with a rails 3 app right now and I have not noticed any problems. I would love to hear what everyone else thinks. Is there some big problem hanging out there that I don't know about? James On Sun, Apr 18, 2010 at 12:53 PM, Niket Patel wrote: > That is good to know. I assume you mentioned couchapp use case. > > We are not using couchapp but I think since 0.10 we are seeing good enoug= h > performance only know problem is dynamic queries ( Same problem that > Raindrop have ) for our use case couchdb is good fit. > > I believe need to understand Map/Reduce upfront is biggest problem for an= y > newbie. Performance is never a problem. > > There are other small things like very high disk use. > > > On 18-Apr-2010, at 11:53 PM, Anh <7zark7@gmail.com> wrote: > > That seems unlikely IMHO, we've been perf testing Couch for our usage an= d >> it outperforms a decently tuned Java webapp running on Resin (known for = its >> good performance) by about 2x. It handles the top-end really well, ser= ving >> 50 or 60 times our current load, with slower response, but not knocking >> over, unlike the Java webapp which starts dropping connections >> >