Your main concern should be if packets are being fragmented too much. Your mtu should be set to allow throughput without too much fragmentation. Default mtu is 1500, and is generally optimal for most networks.
Efficiency improves (less overhead vs. payload) as packet size increases. Also, network devices, such as many software based routers, can process a certain number of packets per second which, although decreases as packet size increases, can forward more "volume" as packet size increases. (These are reasons why later Ethernet devices often support some type of "jumbo" packets.)
L2 and L3 have overhead per frame and packet. For instance, a typical Ethernet non-VLAN tagged frame has 38 bytes of overhead (interfame GAP, preamble, src/dest MAC addresses, CRC, etc.) IP has 20 bytes of overhead, mostly IP addresses. TCP usually adds another 20 bytes of overhead (or more with some TCP options). So to send 1 character/byte in a single TCP packet on Ethernet, you're looking at something like 78 bytes, or more, on the wire to pass your 1 byte of data. Rather poor efficiency. As the number of data payload bytes is increased, since overhead stays the same, efficiency improves.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...