incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Julian Moritz <maili...@julianmoritz.de>
Subject Re: performance issues
Date Mon, 05 Apr 2010 18:52:11 GMT
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
> 

Mime
View raw message