That size is based upon the fact that most ethernet networks have an MTU size of around the same number (the MTU being the largest number of bytes that can be transmitted in a single ethernet frame (after adding ethernet headers and the like) without fragmentation; any thing bigger will wind up being split at the IP layer into multiple packets). Since UDP is usually used in an attempt to get the most performance out of the network you want to avoid extra overhead (such as fragmenting and re-assembling) if at all possible (I also see mentions of some OSen not allowing packets larger than a certain size so there could be platform issues involved as well).
Probably the best route would be to submit a patch which provides a user-configurable parameter (RecvSize maybe) which defaults to the current 1500 value.
The cake is a lie.
The cake is a lie.
The cake is a lie.
In reply to Re: 1500 Byte UDP Limit in POE::Wheel::UDP?
by Fletch
in thread 1500 Byte UDP Limit in POE::Wheel::UDP?
by cmv
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |