couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Lehnardt <>
Subject Re: Efficient view design question
Date Mon, 27 Oct 2008 13:03:51 GMT

On Oct 27, 2008, at 12:20, Jonathan Moss wrote:

> The view functions shown above return the whole doc. Which is know  
> is in-efficient. In fact since I already have the document I want  
> the children/parents of, I also already have all the child/parent  
> IDs. Would it be much more efficient to simply retrieve the parent/ 
> child documents individually rather than having to re-generate views  
> all the time?

See 2) at

> As a side question - Having to re-generate views constantly in this  
> kind of a situation could prove a real issue. I know that CouchDB is  
> still pre-1.0 release and the developers are necessarily focusing on  
> 'getting is right' before 'getting it fast' (to coin a phrase :) but  
> will improvements in speed already on the roadmap make these worries  
> moot except in very large databases or is it always going to be an  
> issue and therefore require some clever application design?
> e.g. keeping frequently updated data in a traditional SQL DB and  
> only keep rarely updated data in CouchDB, which would be a shame.

We'll work on improving view creation time. At the moment it is all  
done sequentially. The MapReduce design will allow us to parallelize  
operations which will make better use of your multi-core servers.


View raw message