For me, the speed from home is rock solid. Your mileage may vary of course. :) Again - this is really just a test 'experiemental' Access Point for us. I really just wanted to see how horribly it would fail, in the face of all the 2.4ghz noise. And (to my great surprise) it's clicking along nicely. So, one of these SM's is at my house, and my family uses it as our internet all the time - 4 kids. We have it set at 20 Mbit down and 2 Mbit up and that's exactly what I get at home.
Again - I know they are having to work at it sometimes... my 'Packets per MCS' is lower than I'd predict solely based on the signals and SNR's I have - so its preferring to use MCS11-12 instead of 13-15 and I do see that in some of the statistics... but I'm frankly shocked that it works at all. Here's a screen shot and you can see that it spends quite a bit of time at MCS-11 on the uplink to the AP. And, it's important to state again that there is only 3 clients on this AP right now - two of us at 20m/2m and one client at 3Mbit/500kBit. Both the 20m/2Mbit clients are staff, and the 3m/500k is a customer 7.5km away that we've just moved off of older 2.4 gear, and he's very pleased.
So - we havent really deployed this out on any of our country towers yet. We are still struggling with the 'real time throughput display' on the Access Points. Without that, we can't wrap our heads around how we are going to manage the calls from customer's and us not being able to look and see what everyone on the Access Point is doing at that moment in real time. However - as far as the 2.4Ghz goes, I'm expecting it to work even better than it does in town of course, so I'm expecting that it'll be night-and-day better than our older non-cambium-brand radios. :)
Yes, this is a GPS equipped AP, and I'm using 20 Mhz wide, and I'm using 5ms frame size. Right now, I'm in 'Flexible Frame' because we don't have any other ePMP or Canopy 2.4Gzhs AP's on that tower.
If your question was leading into latency - this is pinging from my desktop at work - to my SM at home (~4km away). So, this is from my Windows PC, to the switch - out the AirFiber24 backhaul, up to the building top where this AP is - through that switch/router - to the ePMP Access Point (which takes 1-2ms for me to ping the AP) and then over the air to my house. It's 5:30 PM so the bazillion routers between here and my house will be reasonably noisy right now...
So - this is GPS/TDD 5ms Frame Time, Flexible Frame. That's 8ms average from my desktop computer at work, to the SM on my roof.
If I switch to TDD Fixed Frame - this is 5ms Frame Time, 75%/25% Fixed Frame. 15ms Average.
And - this is TDD 2.5ms Frame Time, 75%/25% Fixed Frame, back to 8ms average ping from my desktop computer at work, to the SM on my roof at home.
As far as Cambium's ''extra'' latency... where we are located - we are about 30ms to Google, so I'm not too concened if our over-the-air latencyis 8ms or 15ms - so the difference between the customer being 38ms vs 45ms from Google makes very little difference in real world performance.
I think what is important in latency is reasonably stable latency, reasonably predicable latency, and I want it to stay reasonably flat as we scale, or reasonly flat if there is some traffic going across the link. WIth our older (non-Cambium) gear, it is basically WiFi gear and it has only 1-2 ms over the air..... until a customer starts using it, and then it's 80ms or 62ms or 214ms or 12ms or whatever. And until we connect the 24th client on the AP, and then everyone's latency is ???ms.
