Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of djc.ochtman@gmail.com
 designates 74.125.82.180 as permitted sender)
MIME-Version: 1.0
Sender: djc.ochtman@gmail.com
In-Reply-To: 
 <CABvT1DF1cqxOiHuJtGe11187GHzA47_OW=_pCN+0F5o_7FGEAQ@mail.gmail.com>
References: 
 <CA+Y+447y6kT_kSz-jan89btUG02M=RDpEiKGjJ2gq_p2afTyrQ@mail.gmail.com>
 <CAJNb-9p-AY7n5Qhavis721KHg0yn2y5J0d9jMWN7_VRwWuWmAQ@mail.gmail.com>
 <CAN-3CB+qW-bofvg2hLAmFSnsWaqZBZ2GwiKsztJ=_MDmckk=iw@mail.gmail.com>
 <CABvT1DF1cqxOiHuJtGe11187GHzA47_OW=_pCN+0F5o_7FGEAQ@mail.gmail.com>
From: Dirkjan Ochtman <dirkjan@ochtman.nl>
Date: Fri, 11 May 2012 14:35:09 +0200
Message-ID: 
 <CAKmKYaCLpPyM6+Vt72KNEdJ_x=jXhUYQfWe7E-1UYfkPSh6fdg@mail.gmail.com>
Subject: Re: Post-mortem
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=UTF-8

On Fri, May 11, 2012 at 2:29 PM, Robert Newson <rnewson@apache.org> wrote:
> Making a single view indexing process faster keeps coming up. For one
> thing, it's not that easy, otherwise it would have been done by now.
> For another, this problem vanishes when you shard (and the BigCouch
> merge will bring this to CouchDB).

What does sharding mean in this context? Running CouchDB/BigCouch on
multiple servers, or just running multiple processes on a single box?
If the latter, why can't we run multiple threads/Erlang processes
within a single shard/OS process? If the former, that's kind of silly,
in the sense that building indexes (at least for me) is CPU-bound but
leaves many of the cores in my server idle.

Cheers,

Dirkjan