I’m implementing a solution with multiple .Net Mobile clients that runs couchbase lite, and sync documents through sync gateway.
I’m testing couchbase lite against a big number of documents.
Let’s say we have 100k document per Client, the Client is authenticated on the Gateway using the user “stressuser1”.
The pull request ends in a few seconds. It logs a hundred of lines like this:
16:15:48.482681 HTTP: #057: PUT /syncdatasampledb/_local/cdcec8cd4951410c5a046bca413f704095a0bd2c (as stressuser1)
When i launch the pull request, Sync gateway takes a lot, it seems it process every document for the channel interested. It logs many lines (one per document?) that looks like this one:
2015/03/12 16:06:51 go-couchbase: call to Do("_sync:user:stressuser1") in github.com/couchbaselabs/go-couchbase.(*Bucket).casNext took 1m2.031121565s
16:06:51.061736 HTTP: #1386: POST /syncdatasampledb/_revs_diff (as stressuser1)
If the push works this way (one like per documents check), i can not use sync gateway for many documents.
Does anyone have tested the sync gateway and mobile lite over many documents, or has any kind of suggestion?
At present I’m thinking about writing those documents to the Server using the CouchBase SDK, then I’ve to exclude those documents from any update, event from the shadow bucket gateway update, if possible.
Thank you for any suggestion.