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)
Message-Id: <B3D225BD-C78A-4710-9285-D8FA69AB9377@apache.org>
From: Jan Lehnardt <jan@apache.org>
To: user@couchdb.apache.org
In-Reply-To: <ec7a93a0906051505h77399e83kea72b02bc2285975@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: Optimizing view building
Date: Sat, 6 Jun 2009 00:18:34 +0200
References: <8ffb00ae0906051323u4f8e6c6uea4f398853db724b@mail.gmail.com>
 <ec7a93a0906051505h77399e83kea72b02bc2285975@mail.gmail.com>


On 6 Jun 2009, at 00:05, Randall Leeds wrote:

> On Fri, Jun 5, 2009 at 16:23, Nadav Samet <thesamet@gmail.com> wrote:
>
>> Hi,
>>
>> I have a 600k documents in one database and building a view (with a  
>> trivial
>> map function) takes about 40 minutes on a single core server. I was
>> wondering if there's a way to tell how the time is divided between  
>> running
>> the javascript map function and actually building the view.
>
>
> The javascript runs in a separate process so you could watch the CPU  
> time
> for beam vs the couchjs process.

beam & couchjs wait for each other while the respective partner process
is working. There is room for optimization, we haven't gotten around to
that yet :)

See this and the dev@ mailing list archives for detailed discussions.

Cheers
Jan
--