We have in our company two mobile apps using couchbase on the server side.
On of them works with binary data and not using views and json docs.
The second one (the new one that is still not in production) use json docs and views.
The first is already in production and has 10 nodes on one cluster of couchbase server 2.2.
We plan to use those 10 nodes also in the second app but there are some question we have before deciding to do that:
We need to change the index_path of the second app to second disk (not the main one) to improve the views performance…how will it affect the first app that is already in the cluster we are changing the views path for?
Is restart needed after changing the index_path?
If we use like 3 design docs with 5-6 views on each…how can it affect the existing first app (that has only binary data) but existing on the same cluster but in different bucket?
Hope to get some help figuring out what is the best solution here.
Separating the index path from the data path is going to improve disk IO performance, especially if you have multiple buckets on the same cluster. This also improves a lot with 3.0 as the views are updated directly from memory asynchronously. On retrieval, it still uses a scatter gather operation from disk. As far as processing cycles, if you’re using stale=false in your view queries, and have a high workload load, it will use cycles in updating the views (an all views within a specific design doc) before each query is processed.
@tgreenstein - so if i have a working cluster with 10 nodes that has only binary data.
and now i want to work with the same existing cluster also with views and json docs and want the index_path to be different from the json docs and binary docs,do i have to create new nodes?? are you sure i cannot change the index_path and restart the existing nodes?