Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 25248 invoked from network); 13 Jan 2010 23:15:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 13 Jan 2010 23:15:00 -0000 Received: (qmail 73972 invoked by uid 500); 13 Jan 2010 23:14:59 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 73910 invoked by uid 500); 13 Jan 2010 23:14:59 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 73900 invoked by uid 99); 13 Jan 2010 23:14:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jan 2010 23:14:59 +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 jchris@gmail.com designates 209.85.222.177 as permitted sender) Received: from [209.85.222.177] (HELO mail-pz0-f177.google.com) (209.85.222.177) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jan 2010 23:14:49 +0000 Received: by pzk7 with SMTP id 7so21443793pzk.30 for ; Wed, 13 Jan 2010 15:14:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=+oVjqZcEev6vczSFBDDgrJIehqMtOAW0N9LDUodVJhE=; b=R0OeMJ4pdUUwo4nHGPx8CSxPyMH2zbXWtiL9bsj1u9tT1kP0ZtypzhgO4U9oEfBcLH Vzh+G7I5sQivKWy6lBqG8XN3cgPzmEBVceDFTmhCRn8Wz34fCOBF0ibj0i3OFb/3Hjvn m9/kmJmWFl9wX+F+jup+geJkNTTID9tMjcuKI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=RryXR7mMH0csBnVhaFrtyxgDvbTRt3GTPCDnwpSp1U1fSvnbTyFkuyslfdg+rwp/mS anmti4XuooEZZah1ikN4w3AUieQ1UDUECzhKENDqgYs72swDESFtwQkSMRZo9F5k3QpS 8GrJb03kkyKHQ6aymy2J2kL5c2CsASZTHA260= MIME-Version: 1.0 Sender: jchris@gmail.com Received: by 10.143.27.37 with SMTP id e37mr2781815wfj.234.1263424468053; Wed, 13 Jan 2010 15:14:28 -0800 (PST) In-Reply-To: References: Date: Wed, 13 Jan 2010 15:14:27 -0800 X-Google-Sender-Auth: 6b4324cc64eb3dd3 Message-ID: Subject: Re: Objective criteria From: Chris Anderson To: dev@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Jan 13, 2010 at 3:02 PM, Roger Binns wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > [I wrote a personal query to Damien which he asked me to repeat here.] > > Both 620 and 623 were closed by Damien because they lacked objective > criteria. =A0For both tickets there are criteria I consider objective :-) > There are also suggestions on how to address the issues. > > Consequently my query is if the criteria are not objective enough, does > Damien not agree with them, not care about the underlying issues, think t= hat > a 10 million document/2GB raw json data set is outside the scope of what > CouchDB should cope with, want this stuff in the wiki etc? I think the first step is to write measurements. Good job, you've done this= . The ticketing system should be for smaller scope issues, I think. Optimizing the view server is an agreed goal of the community. Probably the best way to help is to take a look at all the work Damien's done in trunk (the pipelining) and perhaps the parallel writers optimization he has. We could really use a way to take the benchmarks you ran, and put them into the buildbot. If you think the high-consistency design can never meet your needs, you should work on alternate indexers. However, there are a lot of low-hanging fruit around - I think we can be fast enough. The key is to approach them constructively, and realize that there's already a lot of working going on along these lines. The best time to create tickets for larger issues, is when you have code. For small bugs, it's good to create a ticket so we don't forget. I'd love to see something like your benchmark harness moved into the build process. Chris > > Roger > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAktOUP4ACgkQmOOfHg372QS/hQCfSP9Edy+wrZRFwItFmDD3mNcN > yyIAn2z9XvJigm2xKk/r4CgAUqZp1t/i > =3DJMLG > -----END PGP SIGNATURE----- > > --=20 Chris Anderson http://jchrisa.net http://couch.io