This will avoid the sending of a segment (packet) with just a few bytes in it. Make writes equal to or slightly less than, a multiple of MTU size.To avoid data copies in the kernel, make write sizes greater than 936 bytes.Our measurements indicate that the overhead of TCP compared with UDP is negligible, especially if optimum write sizes are used. If the requests or responses are variable-size, use TCP with the TCP_NODELAY option.This may not be possible on a server that is communicating with a number of clients via a single socket. Whenever possible, use the connect subroutine to associate an address with the UDP socket.In general, it is more efficient for the application to write large messages and have them fragmented and reassembled by IP, than to have the application write multiple times.If possible, make the write sizes equal to (a multiple of the MTU size minus 28 bytes to allow for standard IP and UDP headers).If the requests and responses are fixed-size and fit into one datagram, use UDP.For maximum bytes per second, use messages that are at least 1000 bytes and equal to or just less than a multiple of 4096 bytes.For maximum number of transactions per second, use the smallest feasible messages.Maximizing Throughput Request-Response Protocols Some recommendations apply to one or the other some apply to both. You can choose to tune primarily either for maximum throughput or for minimum memory use. Tuning, followed by specific recommendations for the different types of LAN. The following sections describe the global principles of communications AIX Versions 3.2 and 4 Performance Tuning GuideĬommunications parameters vary with the type of LAN as well as with theĬommunications-I/O characteristics of the predominant system and application
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |