So I found out that my beta tester has an ADSL Internet connection with about 20 mbit/s download speed and about 2 mbit/s upload speed.
Because replication is doing a lot of uploading, it's saturating his available bandwidth. And because he has an ADSL connection I've read, the download performance can suffer greatly when you're using up a lot of the upload bandwidth. He showed me some speedtest.net output and I can definitely see that when my app is replicating, his performance drops considerably during the speed test. I have a very fast cable connection to the Internet with approximately 120 mbit/s download and 10 mbit/s upload speed. I noticed that while I was replicating a new database with 117,000 documents in it, I was using up just over 2 mbit/s of my upload bandwidth according to speedtest.net. But I still had plenty of bandwidth left of course. In fact, while I was doing all this testing I also was watching a show on Netflix. I still had plenty left even with that. I read an article about this ADLS problem and they said the only solution is to have the application throttle the upload speed so it doesn't consume so much of the upload bandwidth. Anyway, just thought I'd update this thread with my findings. Thanks, Brendan On Friday, May 20, 2016 at 6:05:13 PM UTC-6, Jens Alfke wrote: > > > On May 20, 2016, at 1:54 PM, Brendan Duddridge <[email protected] > <javascript:>> 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/953906f6-08c7-4f2a-aa8b-9375de3c844b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
