From user-return-9758-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Mon Apr 05 18:52:37 2010 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 73089 invoked from network); 5 Apr 2010 18:52:37 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 5 Apr 2010 18:52:37 -0000 Received: (qmail 82943 invoked by uid 500); 5 Apr 2010 18:52:36 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 82876 invoked by uid 500); 5 Apr 2010 18:52:36 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 82868 invoked by uid 99); 5 Apr 2010 18:52:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Apr 2010 18:52:36 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [62.146.15.6] (HELO mars.a1a-server.de) (62.146.15.6) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Apr 2010 18:52:28 +0000 Received: from localhost (localhost [127.0.0.1]) by mars.a1a-server.de (Postfix) with ESMTP id 4F7DDE1663 for ; Mon, 5 Apr 2010 20:52:08 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mars.a1a-server.de Received: from mars.a1a-server.de ([127.0.0.1]) by localhost (mars.a1a-server.de [127.0.0.1]) (amavisd-new, port 10024) with LMTP id jX522ejfFXDG for ; Mon, 5 Apr 2010 20:52:05 +0200 (CEST) Received: from [192.168.178.32] (unknown [188.106.6.35]) (using SSLv3 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mars.a1a-server.de (Postfix) with ESMTPSA id F39EFE164C for ; Mon, 5 Apr 2010 20:52:04 +0200 (CEST) X-DKIM: Sendmail DKIM Filter v2.6.0 mars.a1a-server.de F39EFE164C DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=a1a-server.de; s=mars; t=1270493525; bh=25WXuQNH7apN3u5z712EaTqIV56Y2eDffIjGiEeFDaI=; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=IijHpnkXnReB uC66NHRPt5rJps1CSXNxdO5DvNpubNG3K9drzIFIi3IYP0S0Xcw498YmaDTFWyrRqSG fkkZl/D6YstC8DlhU8wprkOMByVs3GMJgiAE96tIzj6OqnppTdbmUWdaEZHazUJvIUA DuxaGFrR5p9XB2Jcxx9Xu97oo= Message-ID: <4BBA315B.5010701@julianmoritz.de> Date: Mon, 05 Apr 2010 20:52:11 +0200 From: Julian Moritz User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: user@couchdb.apache.org Subject: Re: performance issues References: <4BBA0C4A.9080304@julianmoritz.de> In-Reply-To: <4BBA0C4A.9080304@julianmoritz.de> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, Julian Moritz schrieb: > Hi, > I've just found this via google: >> We don't parallelize view index creation yet, so this is not an >> additional problem for you. You can however build two views in >> parallel and make use of two cores that way. > If this is (still) true, view index creation is the bottleneck of my application. Hence I'm just playing around and yet using 100% of my core, I cannot use CouchDB anymore. Regards Julian > I've developed a (in my eyes) simple view. I have a wordlist which does > not contain unique words. I want to store it in a view, with every word > occurring once and ordered by random. Therefore I have a simple view > function: > > function(doc){ > emit([hash(doc.word), doc.word], null); > } > > and a simple reduce: > > function(key, values, rereduce){ > return true; > } > > calling that view with group=true it does what I want. > > When storing plenty of words to the database, one of my two cpu cores is > used completely by couchjs. > > Isn't the view built using two (or all) cpu cores? I thought (obviously > I'm wrong) that it would be calculated in parallel and using a > quadro-core (or more cores) would make storing faster. > > Is there a solution for that? Should I use another query-server? > > Regards > Julian >