First World Problems
Posted: Thu Sep 28, 2017 9:36 am
At the modem, speedtest.net measures 105 Mbps (Cox Cable). Directly out of the MX64, speedtest.net measures 103 Mbps. In a clerk's office, behind a cheap Monoprice switch, through a garbled patch panel, and easily 200 feet away, speedtest.net measures 101 Mbps. Standing 5 feet away from the MR33, plugged directly into the MX64 (7 ft cable), but for the Ubiquity POE injector, 48 Mbps. The same laptop was used for all tests. Now, I know that wired Ethernet is always faster than WiFi. I wasn't expecting a 50+ percent difference. Still, the new MX64s blow the doors off the old Cisco 881s.
My Stake Presidency is aggressively trying to establish a robust effort in family history work in our stake. Two nights ago, one of our wards held a Family HIstory Indexing workshop. With 28 laptops, all in varying stages of activity, I measured the same ~48 Mbps, and, got a lot of thumbs up from the leaders and many in attendance. Last night, a smaller familysearch.org workshop reported a less than ideal experience, despite the fact I had the same MR33 resting on the table in front of them. In this case, the MR33 was behind 200+ feet of cable, and the best measurement on speedtest.net was ~ 39 Mbps. I realize that indexing vs research on familyhistory.org are two drastically different things and the likely cause of any delay of the latter is server-side related and should be expected. I'll try and be there in person next Wednesday when they do it again.
Is the Meraki system throttling speed tests? I've read that one of the features included in the Meraki management is the ability to keep abusers from hogging bandwidth. I suspect this to be the case because despite measuring 48 Mbps, I couldn't stream a YouTube video in any quality over 360P (via WiFi) when I was the only person in the building. The Cisco 702s are no longer available in the church store. We've got more than a year until the full Meraki rollout is complete worldwide. I don't expect to see additional MR33s anytime soon. And even if/when we do get more, it's not going to improve WiFi speed, just coverage. I think it's time to tell everyone (including and especially myself),
"This is as good as it's going to get. It's better than most, just do the best you can."
My Stake Presidency is aggressively trying to establish a robust effort in family history work in our stake. Two nights ago, one of our wards held a Family HIstory Indexing workshop. With 28 laptops, all in varying stages of activity, I measured the same ~48 Mbps, and, got a lot of thumbs up from the leaders and many in attendance. Last night, a smaller familysearch.org workshop reported a less than ideal experience, despite the fact I had the same MR33 resting on the table in front of them. In this case, the MR33 was behind 200+ feet of cable, and the best measurement on speedtest.net was ~ 39 Mbps. I realize that indexing vs research on familyhistory.org are two drastically different things and the likely cause of any delay of the latter is server-side related and should be expected. I'll try and be there in person next Wednesday when they do it again.
Is the Meraki system throttling speed tests? I've read that one of the features included in the Meraki management is the ability to keep abusers from hogging bandwidth. I suspect this to be the case because despite measuring 48 Mbps, I couldn't stream a YouTube video in any quality over 360P (via WiFi) when I was the only person in the building. The Cisco 702s are no longer available in the church store. We've got more than a year until the full Meraki rollout is complete worldwide. I don't expect to see additional MR33s anytime soon. And even if/when we do get more, it's not going to improve WiFi speed, just coverage. I think it's time to tell everyone (including and especially myself),
"This is as good as it's going to get. It's better than most, just do the best you can."