Technically speaking, you would be incurring less overhead if you had all views in one design document vs. spread out. The reason being that for each design doc, documents have to be serialized to json and then the results are de serialized.
There are two main thoughts at the moment. Group views like you have by data that is indexed, or group everything required for a given application in a single design doc. The second method is running on the idea that design docs have a 1 to 1 correspondence to applications. Paul On Sun, Nov 2, 2008 at 5:23 PM, Ask Bjørn Hansen <[EMAIL PROTECTED]> wrote: > Hi, > > I'm using 0.9.0 (svn trunk). What's the best way to organize the design > documents? In the DB I'm working on I have three design documents (with 1, > 2 and 3 views respectively); roughly organized by "which data is indexed". > Does that make sense? > > If I understand it right, then each design document updates separately, but > all views in a design doc are updated together. Given that, does it make > more sense to split them up further; or do I get some performance benefits > from updating more of the documents together? > > > - ask >
