Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAKrexVKY4zpAF4t268CDL=xVr-sx_ZPmr67R9V=mr4pp3FRvpw@mail.gmail.com>
References: 
 <CAAOi-OE9BkwbgX9ocRxZKzgDh8C=nP-brpW9phmrQGhf=J1tug@mail.gmail.com>
 <CABvT1DFqdae0kUdRWfPuXyThv9cRh21N=o6AW0o-bU383K7Nxg@mail.gmail.com>
 <CAAOi-OFPLeTiV1+2XT742aeP=YFCg9NE6qHpno=HQfNW7F2QEQ@mail.gmail.com>
 <CABvT1DHV2Ljgnqw47xxsBnUzjnSamAsSk5mJYmxUWJSsJ4efHg@mail.gmail.com>
 <CAMiZLn1WeYWf+isPAaYCKZXFfBxrAAqnQ=e6E1VztYgha-HxGg@mail.gmail.com>
 <CAHFJ+K6xKpbHtNL4y8gvpMNhzSMCBuQGtVNFnG1rN1SZTMqeTA@mail.gmail.com>
 <CAMiZLn1Qa5i6zPOoMPudo74MtkhujHGJQXrNuhVqwRtLiv8tTA@mail.gmail.com>
 <CAKrexVKY4zpAF4t268CDL=xVr-sx_ZPmr67R9V=mr4pp3FRvpw@mail.gmail.com>
From: Daniel Gonzalez <gonvaled@gonvaled.com>
Date: Thu, 15 Mar 2012 09:48:05 +0100
Message-ID: 
 <CAAOi-OGLVTLNiJxpDoWpuo8yUqZzt_h1rXm0GzH7v82J5itCJw@mail.gmail.com>
Subject: Re: Creating a database with lots of documents and updating a view
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Cgs,

I suppose I could come up with a partition strategy that distributes
the load: I could do what you suggest, or I could also use separate
hosts. But all this would transfer complexity to my application, and I
want to avoid that.

Thanks
Daniel

On Thu, Mar 15, 2012 at 12:41 AM, CGS <cgsmcmlxxv@gmail.com> wrote:
> Hi,
>
> Sorry for interfering, Daniel, but do you really need all those documents
> in a single database? I mean is it mandatory to have them there? Because =
if
> not, one can split that 3M database in 10 - 100 smaller databases, each
> with its own view, and concatenate the result after that (if you cannot u=
se
> pagination, otherwise, instruct your view to take only a certain number o=
f
> results per displayed page) using JS or whatever else if you have an
> application which needs that result. In this way you can have a certain
> level of parallelism which may speed the overall process.
>
> Just a 2c idea.
>
> CGS
>
>
>
>
>
> On Thu, Mar 15, 2012 at 12:13 AM, Matthieu Rakotojaona <
> matthieu.rakotojaona@gmail.com> wrote:
>
>> On Wed, Mar 14, 2012 at 10:19 PM, Christopher Sebastian
>> <csebastian3@gmail.com> wrote:
>> > I am also new to couchdb, but I don't believe the information from
>> Matthieu
>> > Rakotojaona is correct. =A0It is my understanding that pretty much
>> everything
>> > in CouchDB (including views) uses incremental updates. =A0So adding ne=
w
>> > documents to the database does NOT cause all view leaves to be travers=
ed
>> --
>> > the view is updated incrementally.
>> >
>> > Is this correct?
>> >
>> > ~Christopher Sebastian
>>
>> I might have spoken a little bit too fast. Indeed when you add new
>> documents, they are automatically passed (or rather they will be when
>> the next query comes) to the map function, which doesn't traverse the
>> already indexed db.
>>
>> But when (and if) you have a reduce function, all the intermediary
>> rereduce results will have to be updated, right ?
>>
>> --
>> Matthieu RAKOTOJAONA
>>