Hello folks

I have simple PtP link
AP: DISC Lite5 ac
CPE: QRT 5 ac

Wireless protocol NV2 kinda works but slow, 802.11 gives better throughput, but does this:
Reply from 172.17.31.202: bytes=1450 time=3ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=4ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=3ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=5ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=6ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=5ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=3ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=5ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=4ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=4ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 172.17.31.202: bytes=1450 time=312ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=6ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=6ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=4ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=33ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=3ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=4ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=6ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=3ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=4ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=4ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=7ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=11ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=5ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 172.17.31.202: bytes=1450 time=10ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=10ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=5ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=5ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 172.17.31.202: bytes=1450 time=448ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=5ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=11ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=11ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=6ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=5ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=4ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=5ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=3ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=5ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=4ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=3ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=8ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 172.17.31.202: bytes=1450 time=244ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=6ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=5ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=4ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=4ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=5ms TTL=64
Reply from 172.17.31.202: bytes=1450 time=13ms TTL=64

nv2 doesn't do this...

I have heard that there is incompatibility between mipsbe and arm hardware. Is this the case?
And what should I do for bettter performance:
Change AP to mipsbe?
Change CPE to arm?

I want to use vanilla 802.11, because it is more sophisticated for AC then nv2, true or not?

Thanks.

My experience so far:

I have no problems between SXT SA5 ac (Mipsbe) and SXTsq ac (ARM). (ROS 6.45.6)

802.11ac is somewhat faster, but nv2 performs better when the fresnel zone is contaminated (trees).

802.11ac follows all wifi rules for media clear /media contention. 802.11 shares airtime with all other 802.11 senders (AP and client) even when their level is extremely low (-96dBm).
Check co-channel and adjacent channel interference. See whatever "snooper" can detect.
Make sure that "station-roaming" is not enabled on the CPE side.
Also check the wireless registration for RX/TX rate, number of streams, RX/TX retransmits and CCQ when the ping times out.

Thanks for the tips.