Thanks for the thoughts guys. I'll move the view in to a separate design document and try assigning unique IDs to dishes and putting those IDs in the view index rather than the full dish title (at the moment there is no item_id, but I can add one).
Each dish in an order tends to be different - an example order might be "Margarita Pizza", "Garlic Bread", "Can of Coke", so the pre-reduce method wouldn't help much in my situation. Thanks, Nick On Thu, Oct 7, 2010 at 4:55 AM, Simon Metson <[email protected]>wrote: > Hi, > > > If that one view has caused your view indexing times to skyrocket, I can >> only assume that you have lots of items per order. You might want to try >> doing some pre-emit reductions in the map function to reduce the number of >> total rows in the view. >> > > You could also move the slow view off into a separate design document, > especially if access times are different (e.g. this view is something used > for a weekly report, vs other views that are consumed by the visitors on the > site). > Cheers > Simon >
