wohali commented on issue #544: "Reduce output must shrink more rapidly" misrepresents which view is problematic URL: https://github.com/apache/couchdb/issues/544#issuecomment-304465038 I want to be careful about saying it's a universal truth of one-view-per-ddoc. The main value in multiple views per design document is to control the amount of couchjs parallelism on your server (modulus the ini file setting to control the max. number of couchjs processes spawned at once). Move to a single-view-per-ddoc approach and on a busy DB that uses all views, for unbuilt views you can starve some views while they wait for a free couchjs process. Generally for a machine 100% dedicated to CouchDB you want to target approximately (cores - 1) couchjs processes, so that would be the equivalent number of ddocs building at the same time. If your views are largely prebuilt, the document churn in them is fairly static and the views don't need a lot of time to constantly build, # of ddocs has less of an impact. As always, performance test your specific situation to get the data you need - CouchDB's performance is very much data dependent. :) ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
With regards, Apache Git Services
