58 MDS iNET 900 User’s Guide MDS 05-2806A01, Rev. A
• 66 bytes—Total Over-the-air bytes for RTS/CTS with PHY
headers.
If the frame is TCP, then there is a 32-byte TCP header instead of the
4-byte UDP header.
• ARP requests, ARP replies and BPDU’s will affect throughput.
• ARP requests are 60-byte Ethernet frames. 142 bytes
over-the-air.
• ARP replies are 60-byte Ethernet frames. 142 bytes
over-the-air.
• BPDUs are 60-byte Ethernet frames. 142 bytes over-the-air.
Note that the overhead to put a single Ethernet frame
over-the-air is 82 bytes. If RTS/CTS is invoked, it is 148 bytes.
Therefore, the overhead for a minimal Ethernet frame
(60 bytes) is 128% and, as such, gives the iNET a poor small
packet performance.
If any iNET in your iNET network is connected to a large LAN, such as
may be found in a large office complex, there be undesired multi-
cast/broadcast traffic over the air.
4. Station-to-Station Traffic
• When sending frames from an endpoint connected to one iNET
station to another endpoint connected to a different iNET sta-
tion, the throughput will be halved at best. This is because all
frames must go through the AP. Therefore, in the previous
100-byte UDP example, the number of over-the-air bytes will
be 380 bytes (190 bytes x 2) if the frame has to go station-to-sta-
tion.
5. Interference has a direct correlation to throughput.
• Interference could be caused by any unnecessary traffic on the
network from unrelated activities, or Radio Frequency Interfer-
ence in the wireless spectrum.
2.8.2 Tips for Optimizing Network Performance
Here are some suggestion on things to try that may maximize
throughput:
1. Increment the
Dwell Time to the maximum of 262.1 ms. This lowers
the overhead since it will stay longer on a channel. The down side is
that if a particular channel is interfered with it will take longer to
hop to another channel.
(
Main Menu>Radio Configuration>Dwell Time)
To Next Page
Loading...
