So we've finally decided that we would take the plunge and see what we can acheive with NV2. A bit of background; we have around 100 transmission towers; well over 250AP's, and many MANY clients
We've been operating for about 7 years, exclusively Mikrotik. Clients range from RB112 / 133 / 411 / 711 ... you get the idea. Distances in this test are upto 34km; channel widths vary; signal strengths vary and i will do my best to give exacts.
We have been hugely vocal with MT on these forums and via support@, giving MT staff heaps of grief about early releases and bugs ; they will know who we are
I thought it was about time that we showed them that the effort they are putting into their new releases is really really really appreciated! 5.7 so far has been amazingly stable for us (and we use snmp, nstream, nv2, mpls, vpls, bgp, ospf all on one 433 in some sites) so thats saying something! MT we really do love you!!!!
Anyway, Down to the the testing.
AP's were set with NV2, 3ms, 10km
We switched 3 of our sites and all associated clients over to ROS 5.7 & NV2 from 4.16 Nstream (we didnt bother testing NV2 with previous versions).
First site had 3 clients
Second site had 6 clients
Third site has 9 clients
We do have sites with over 40 clients; we havent migrated these yet as we are still very much in testing with Nv2 and didnt want th stress! as mentioned above clients run a whole variety of hardware platforms.
First site runs Vlan back to our MPLS core
Second site has OSPF, MPLS and BGP on it
Third site runs vlans back to MPLS code
Testing was from the client to the AP directly.
First site is 433
Second site is 433AH
Third site is 333
Signals of the tested clients range from -55 to -80
First site clients went from acheiving approx 12mbit (from nstream, 10mhz channel width to NV2) to 18.5mbit! No other changes!!!
Second site clients went from acheving approx 8mbit (from nstream, 10mhz channel width to NV2) to 17mbit!!!
Third site clients went from 8mbit sold to (from nstream, 10mhz channel width to NV2) 18mbit
Latency at idle was bouncy, upto 50ms, under load, no more than 20ms (for all 3 AP's) mostly hanging around 9 to 12ms. I guess using 3ms increased the latency to this point.
I understand that Nv2 ignores locked data rates; which under nstream **ALL** clients were locked to 24mbit, A mode only. Testing was only one client at a time. Aggregate throughput when testing multiple clients remained within about 500k of the max throughput seen from one client only.
Now for the P2P test.
This link is 34km, -78 signal (not great) 20mhz channel width. Nstream gets 28mbit one way (802.11N); NV2...very very poor and bouncy between 17mbit/24mbit. So it seems that with a less than awesome signal over long distances in a P2P enviroment Nstream still wins, hands down. Again this was set to 3ms 35km.
Take from this what you will, but we are impressed. VERY impressed. We will monitor over the next 14 days and check for memory leaks or any other odd behavior and then move to upgrade our entire platform to 5.7.
Final word, WELL DONE MIKROTIK!!!!!!!!!!!!!!
Edit: this message got declined from posting due to too many smiles!