Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <20130306133305.164ae757@svilendobrev.com>
References: 
 <CAAOi-OGijL+DEN+1L7TncmFHo48U+STPLCOWruMSinaA=tP9NQ@mail.gmail.com>
 <20130306133305.164ae757@svilendobrev.com>
From: Anthony Ananich <anton.ananich@inpun.com>
Date: Wed, 6 Mar 2013 15:13:42 +0300
Message-ID: 
 <CAFANTuXSrnt4d0UXYVj+hkzvCAUNX9Am4E27pHHidmZ7oTZF4A@mail.gmail.com>
Subject: Re: Update handler is very slow
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1

And how much does it take to add document by HTTP PUT?

On Wed, Mar 6, 2013 at 2:33 PM, svilen <az@svilendobrev.com> wrote:
> +1. i'd like to know also about update_handlers as i may get into such
> situation soon.
>
> not an answer:
> if you sure your transformation is correct, my lame take would be:
> don't do anything.
> 4doc/s, 12000/hour - so by tomorrow it would be done.
>
> of course, no harm to find/learn - e.g. u may need to rerun it again..
>
> ciao
> svilen
>
> On Wed, 6 Mar 2013 12:06:41 +0100
> Daniel Gonzalez <gonvaled@gonvaled.com> wrote:
>
>> Hi,
>>
>> We have a problem in our data: we have been inconsistent in one of our
>> fields, and we have named it in different ways. Besides, in some
>> places we have used int, in other places string. I have created an
>> update handler to correct this situation, and I am running it for our
>> 100 thousand documents database, by doing PUT requests, as explained
>> http://wiki.apache.org/couchdb/Document_Update_Handlers
>>
>> What I am doing is:
>>
>>    1. get affected documents with a view
>>    2. call the update handler.
>>
>> And this is running over an ssh tunnel.
>>
>> My problem is that this is veeeery slow. Currently I am running at 4
>> docs/s. Is this normal?
>>
>> I could do this locally (no ssh tunnel), but I guess things would not
>> improve much, since the data being transferred is not that big (no
>> include_docs, and the view emits very litte information). I have the
>> impression that the bottleneck is couchdb itself: the update handler
>> is just that slow.
>>
>> Am I right about this? Is there a way to speed this up?
>>
>> Thanks,
>> Daniel