couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcello Nuccio <marcello.nuc...@gmail.com>
Subject Re: view index generation for single document and bulk documents
Date Thu, 16 Jun 2011 07:36:23 GMT
2011/6/16 Yogesh Khambia <ykhambia@gmail.com>:
> Hi Marcello,
>
> Thanks for the tip.
> I will be testing with CouchDB-1.1 soon.
> One point I want to add:
> In my case as the database is being updated quite often, the user is
> interested in the view on the latest data available at any time. Querying
> the view with 'stale=update_after' parameter will result in stalling the
> view and then rebuilding the view index, therefore, it will not give the
> view on the latest data.

It will give the view on the latest indexed data and it will ensure
that the index is kept updated. It's a trade-off. What is the most
important for your users: fast response time or information updated to
the last second?

Marcello

>
> On Thu, Jun 16, 2011 at 7:40 AM, Marcello Nuccio
> <marcello.nuccio@gmail.com>wrote:
>
>> Hi Yogesh,
>> I cannot answer your questions, but I think you should repeat your
>> tests with CouchDB-1.1 and querying the view with `stale=update_after`
>> parameter.
>>
>> Read
>> http://docs.couchbase.org/couchdb-release-1.1/index.html#coudhdb-release-1.1-updateafter
>> for more information.
>>
>> Bye,
>>  Marcello
>>
>> 2011/6/16 Yogesh Khambia <ykhambia@gmail.com>:
>> > Hi all,
>> >
>> > Currently, I am doing performance tests with database in CouchDB 1.0.1,
>> > where a script is continuously writing single documents to the CouchDB
>> > database.
>> > I had the issue of the user being penalized for reading the view in
>> CouchDB
>> > database, by updating the view indexes.To improve on the latency for the
>> > view index generation, I wrote a function which generates the view
>> indexes
>> > for each new update made to the database.
>> > The latency for view index creation has been improved. However, I read
>> from
>> > the FAQ on the CouchDB wiki that "The reason not to integrate each doc as
>> it
>> > comes in is that it is horribly inefficient and CouchDB is designed to do
>> > view index updates very fast, so batching is a good idea."
>> > It will be really helpful if somebody can answer me on following:
>> >
>> > - If  view index generation for each new single document insert is not a
>> > good approach?
>> >
>> > - How does the single document insert and bulk document insert affect the
>> > CouchDB view generation, where:
>> >
>> >   1.  a daemon script updates view index for each new document insert.
>> >   2.  a daemon script updates view index for bulk document
>> >
>> > Thank you.
>> >
>> >
>> > --
>> > Best Regards,
>> > Yogesh Khambia
>> > Postgraduate Design Engineer
>> > Mobile: +31 626 217 381
>> > Email: y.khambia@tue.nl
>> >
>>
>
>
>
> --
> Best Regards,
> Yogesh Khambia
> Postgraduate Design Engineer
> Mobile: +31 626 217 381
> Email: y.khambia@tue.nl
>

Mime
View raw message