I would appreciate any insight I get. Moving forward I wanted to move our entire infrastructure to couchbase, but I first want tot make sure I completly understand it’s performance.
thanks for the detailed description and sorry for coming back to you so late.
I wouldn’t expect it to be so slow. From your code it looks like you’re using the default staleness (which should be update_after. Though can you please try with stale=ok, just to make sure it’s not the indexing that slows things down.
And another note: the approach with the using the location bucket as kind of a cache won’t help for the indexing performance as expiry of documents is the same a delete, which means the index needs to get updated.
I tried things out locally. A dataset with 1M rectangles and a queries that return different sizes. I it with wrk. With 10 concurrent connections I got (I post the maximum latency of each 60s run):
229.19ms for 4 items
552.07ms for 122 items
1006ms for 1334 items
Is your client in the same dataset as your Couchbase instance? Could it be that the network connection is slow? You might want to try raw HTTP requests, to see if it’s some client or server issue.
My test was also on a single Couchbase instance on my local laptop. Could you try doing the HTTP requests directly? Either with nodejs or some other tool?
None of those fixes the problem.
I recently discovered that my index tab is empty: http://puu.sh/l5juX/7cfba2de24.png
It might be that my views are not indexed?
Sorry for the late reply, I somehow didn’t get notified that you posted. The indexing tab is for secondary indexes and not for views. The spatial views will show up in the views tab.
I’m running out of ideas, if I could get access to your dataset (or a dataset that shows similar issues) that would be great. Then I could more easily debug the issue.
