Most people so far seem to be looking at this from a throughput point of view; I’m more interested in the reliability point of view:
Here is a too brief ping test I performed just now:
NV2:
Ping statistics for 10.23.22.1:
Packets: Sent = 100, Received = 99, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 300ms, Average = 48ms
802.11:
Ping statistics for 10.23.22.1:
Packets: Sent = 100, Received = 96, Lost = 4 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 1531ms, Average = 174ms
nstream (via protocol drop-down)
Ping statistics for 10.23.22.1:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 272ms, Average = 43ms
This link is being unusually well behaved right now. In the late evenings it is frequently bad enough to be unusable. I will leave it in nv2 mode for a few days and see how it does.
Personally, I prefer stable links with occasional high latency to ones that drop packets or the entire link all the time; thus hiding packet loss (typically by retransmitting behind the scenes until the packet gets through, and thereby converting packet loss to the appearance of a lower throughput link), than links that pretend they are fast, while having 60% packet loss. I’m hoping this is what nv2, being TDMA, will give me. 802.11 pretends to work this way, but usually just drops the link instead (after a limited number of failed retrys). (Basically, I’m describing Canopy vs nearly everyone else).