On May 20, 2016, at 1:54 PM, Brendan Duddridge <[email protected]<mailto:[email protected]>> wrote:
Hi, I have a beta tester right now who is pulling his hair out of his head because when my app is replicating either between peers using peer-to-peer networking or via the cloud to IBM Cloudant, he says his network performance is suffering. He says that on his iOS devices he's getting kicked off of WiFi and for no apparent reason he's being bumped over to the 4G cellular network. That’s weird; I’ve never heard of a problem like that before*. All we do is regular HTTP requests (ok, and WebSockets for the changes feed, but that’s low-volume). That shouldn’t cause any more trouble than, say, browsing Instagram or syncing your Dropbox. Honestly I don’t think the replicator even has the throughput to saturate a modern WiFi connection. My guess is there’s something screwy with his base station / router. Is this guy technical enough to do some troubleshooting? So I thought I'd ask to see if there was a way that I could enable some sort of request throttling so that replication doesn't use quite so much network resources. We don’t have a setting for that; honestly, we haven’t gotten a request for it, while we do get requests to make replication faster. :/ —Jens * except with BitTorrent, which has the capacity to overwhelm a badly-designed router with traffic, but they switched to the µTP protocol a few years ago to alleviate that. -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/3AA3A4C4-4D49-4E62-AA66-9F60FB89854E%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
