Views and their memcached behaviour
Hi, love what you're doing here with Couchbase 2.0. Really interesting and FAST.
I've evaluated couchDB before I found this project, and I think this fits our needs better, but I have some questions regarding how views work in couchbase.
1. According to the webinars once the production views are generated they will reside in RAM and get updated only when you query them (either on stale=false or stale/update after). But you can choose whether to use reduce in the call. Are both reduced and unreduced data cached in RAM? Are they both generated when you create your view and choose to run in on the whole data set?
2. Same for grouping - you can choose grouping level on query. Are all grouping levels cached in RAM? Considering memcached's background I'd assume they are once they've been queried. Are the view cache dropped using the same rules as regular key/value in RAM or are they dropped sooner/later? (If RAM gets full)
3. In the webinar you mentioned that before publishing a development view into a production view you should run it on the whole dataset so it's already generated and available when you publish the view.
If you run a dev view on the whole data set, how long do you store the view data? Could it be dropped because of high load on the server BEFORE I had time to publish the view as a production view?
thanks in advance and keep up the good work!