Thanks. That’s for Couchbase Server, not the SyncGateway, right? I did find this somewhat helpful:
http://developer.couchbase.com/documentation/mobile/1.1.0/develop/guides/sync-gateway/deployment/in-production/index.html
It drops a some hints, but doesn’t address my questions thoroughly:
1.It says “A quad-core/4GB RAM backed Sync Gateway can support up to 5k users” , presumably this is just an rough guesstimation as it probably depends on the size of JSON and pattern of push/pull replication.
- It says “Because Go uses asynchronous I/O, it’s capable of listening on large numbers of sockets provided that you make sure the OS is tuned accordingly and you’ve got enough network interfaces to provide a sufficiently large namespace of TCP port numbers per node.” This seems to suggest network interfaces/namespace of TCP port numbers per node could be the bottleneck on high load. Then given a limit on this, say 10K, and given the JSON size and pattern of replication, how to calculate the RAM and number of cores for CPU needed?