![]() ![]() In fact, the culprits are none other than TCP and the laws of physics. The traceroute and MTR look finebut where’s the performance and bandwidth you’re paying for This issue is all too common and it has nothing to do with the network. Change this "-w" iperf option to simulate other IBM Spectrum Protect TCPWindowsizes. What’s wrong with the network you wonder. AIX does not have auto tuning abilities so discrete values are recommended. In the case of Windows, Linux and MacOS, the operating system default provides a more dynamic tuning of the sliding window, often providing improved performance. Setting IBM Spectrum Protect TCPWindowsize to 0 instructs IBM Spectrum Protect not to set this value, allowing the operating system defaults to be used. ![]() In 8.1.11 and higher, the value is set to 0 in Windows, Linux and MacOS, and is set to 256 kilobytes in AIX. In IBM Spectrum Protect 8.1.10 and earlier, the default is 63 kilobytes (64512 bytes). This is analogous to the IBM Spectrum Protect TCPWindowSize option available on both client and server, though the IBM Spectrum Protect option is specified in kilobytes not bytes. The "-w 64512" iperf option instructs iperf to set the TCP send and receive sliding window buffers to a certain value in bytes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |