Idle question, aside from other access points and DFS radar, does anything else interfere on 5GHz? I'm going to do some speed tests on between the access point and the switch - and the switch to the router.
Wifi is a dynamic world (on the millisecond), as one is seldom allone using the "ether" to transmit things.
Most things have been said here already. So what follows is a summary and repeating.
Doing overall speed tests is good, as an overall quantification of what can be attained. But it is not good enough for differential diagnosis to find the root cause(s).
(All IT prolems become complex when there are multiple independent causes).
For wifi there are at least three levels: 1. interface rate 2. co channel interference 3. IP protocol
1. Interface rate
Very important to check ! It's dynamic, varies all the time in the real world. Send and receive are 2 separate values. It can be seen in the registration table, with some detail. Typical readout : "400Mbps-40MHz/2S/SGI". MT does not give the MCS level (can be looked up in
https://mcsindex.com/) Here 400Mbps is MCS09 for a 40MHz wide channel (e.g. 20MHzCe) , with dual stream, short guard interval 0.4µs. All can vary : MCS rate, # of streams, guard interval , even the bandwidth can drop, dynamic in time. Wifi devices reduce the interface rate based on failed transmissions, and augment the rate again with succesfull transmissions. Each vendor has its own strategy. Retransmissions can be seen (HW Frames versus Frames), CCQ is a deduction from this. Transmissions fail because of adjacent channel interference, distortion, diffraction and noise with high MCS rates (=high QAM) where the signal cannot be decoded for that QAM. SNR is in the registration table.
Throughput is reduced by retransmission ratio. and It follows also the interface rate !
Going from interface rate to data rate can be calculated:
viewtopic.php?t=165698&hilit=spreadsheet#p912622
2. co channel Interference
It's seldom one is alone on the channel. Co-channel interference or coexistence is gently waiting for each other, based on the timing in the packet headers. Packet headers are received further away than real data can be decoded. Mikrotik is not giving "channel busy" information. Other brands do, and send it even in the AP beacon as QBSS. The contention window (CW) parameter defines the chances to get a free transmission slot. CW parameters are different with WMM for video and voice. (they use smaller values and get much better chances that way).
Some time is lost in management packet overhead. (0.5% for every SSID on every AP if set at 6 Mbps, 3% if basic rate set at 1 Mbps)
Only one can talk in a channel. Data throughput is reduced to free airtime.
3. IP protocol.
The influence of TCP congestion avoidance is not to be underestimated. There are many protocols in the clients (
https://en.wikipedia.org/wiki/TCP_congestion_control ). The impact can be huge, getting lower than 10% usage. Varying wifi transmission conditions can trigger unwanted congestion avoidance actions.
DFS does not slow down the data rate as above. If "radar detected" is triggered, then the AP must change frequencies at once. For a Mikrotik this is for at least 1 full minute no communication possible if another DFS channel is selected.