M
Mats
Hello,
Network
XP Prof FTP Server ---- 1 Mbit/s wireless -------- XP Prof, FTP client
The Round Trip Time (RTT) is about 125ms, i.e. the tcp window size should be
at least 1Mbps * 125ms = 15,6kB
Problem
- tcp window size is correctly negotiated (e.g. 128kB) in the tcp syn
messages at the beginning of e.g. a FTP session.
- During the data transfer, tcp only uses up to ca. 6kB and waits until the
accks are received from the FTP client.
Below is a typical trace extracted from a WireShark trace on the FTP server.
Frame 31760, 31761 an 31762 are send with high speed and than tcp waits 124
ms until the acks are received. Due to these pauses, only about 20% of the
available bandwidth is used. (UDP uses 100% of the available bandwidth.)
31760 214.542589: Send, 64395
31761 214.542591: Send, 65537
31762 214.542921: Send, 66947
31763 214.656427: Ack, winSize = 66947 - 64395 = 2552 Bytes, AckDelay =
000.113838
31766 214.659753: Send, 68357
31767 214.676404: Ack, winSize = 68357 - 66947 = 1410 Bytes, AckDelay =
000.133483
31771 214.681036: Send, 69633
31772 214.681306: Send, 71043
31773 214.796140: Ack, winSize = 71043 - 69633 = 1410 Bytes, AckDelay =
000.115104
31778 214.802790: Send, 72453
31779 214.802791: Send, 73729
31780 214.802792: Send, 75139
31781 214.926274: Ack, winSize = 75139 - 72453 = 2686 Bytes, AckDelay =
000.123484
31785 214.931598: Send, 76549
31786 214.931600: Send, 77825
31787 214.956236: Ack, winSize = 77825 - 75139 = 2686 Bytes, AckDelay =
000.153444
31791 214.961553: Send, 79235
31792 214.961885: Send, 80645
31793 215.056412: Ack, winSize = 80645 - 76549 = 4096 Bytes, AckDelay =
000.124814
31796 215.059407: Send, 81921
31797 215.076382: Ack, winSize = 81921 - 79235 = 2686 Bytes, AckDelay =
000.114829
31802 215.083040: Send, 83331
31803 215.083042: Send, 84741
31804 215.083043: Send, 86017
31805 215.166581: Ack, winSize = 86017 - 81921 = 4096 Bytes, AckDelay =
000.107174
31809 215.171910: Send, 87427
31810 215.172243: Send, 88837
In Microsoft TechNet:
http://technet2.microsoft.com/windo...8b46-4870-a83e-8032637a87c81033.mspx?mfr=true
I have found
"TcpWindowSize
.....
The stack also tunes itself based on the media speed:
- Below 1 Mbps: 8 KB
- 1 Mbps 100 Mbps: 17 KB
- Greater than 100 Mbps: 64 KB"
- Is this true for a WinXP professional? The tcp window size depends on the
RTT and media speed - not only media speed.
- If true, the theoretical max bandwidth is 8kB * 8 bit / 125ms = 512kbps -
never 100% of the vailable bandwidth! (In my case less because of packet loss)
- Is it possible to disable this "tuning"?
Regards, Mats
Network
XP Prof FTP Server ---- 1 Mbit/s wireless -------- XP Prof, FTP client
The Round Trip Time (RTT) is about 125ms, i.e. the tcp window size should be
at least 1Mbps * 125ms = 15,6kB
Problem
- tcp window size is correctly negotiated (e.g. 128kB) in the tcp syn
messages at the beginning of e.g. a FTP session.
- During the data transfer, tcp only uses up to ca. 6kB and waits until the
accks are received from the FTP client.
Below is a typical trace extracted from a WireShark trace on the FTP server.
Frame 31760, 31761 an 31762 are send with high speed and than tcp waits 124
ms until the acks are received. Due to these pauses, only about 20% of the
available bandwidth is used. (UDP uses 100% of the available bandwidth.)
31760 214.542589: Send, 64395
31761 214.542591: Send, 65537
31762 214.542921: Send, 66947
31763 214.656427: Ack, winSize = 66947 - 64395 = 2552 Bytes, AckDelay =
000.113838
31766 214.659753: Send, 68357
31767 214.676404: Ack, winSize = 68357 - 66947 = 1410 Bytes, AckDelay =
000.133483
31771 214.681036: Send, 69633
31772 214.681306: Send, 71043
31773 214.796140: Ack, winSize = 71043 - 69633 = 1410 Bytes, AckDelay =
000.115104
31778 214.802790: Send, 72453
31779 214.802791: Send, 73729
31780 214.802792: Send, 75139
31781 214.926274: Ack, winSize = 75139 - 72453 = 2686 Bytes, AckDelay =
000.123484
31785 214.931598: Send, 76549
31786 214.931600: Send, 77825
31787 214.956236: Ack, winSize = 77825 - 75139 = 2686 Bytes, AckDelay =
000.153444
31791 214.961553: Send, 79235
31792 214.961885: Send, 80645
31793 215.056412: Ack, winSize = 80645 - 76549 = 4096 Bytes, AckDelay =
000.124814
31796 215.059407: Send, 81921
31797 215.076382: Ack, winSize = 81921 - 79235 = 2686 Bytes, AckDelay =
000.114829
31802 215.083040: Send, 83331
31803 215.083042: Send, 84741
31804 215.083043: Send, 86017
31805 215.166581: Ack, winSize = 86017 - 81921 = 4096 Bytes, AckDelay =
000.107174
31809 215.171910: Send, 87427
31810 215.172243: Send, 88837
In Microsoft TechNet:
http://technet2.microsoft.com/windo...8b46-4870-a83e-8032637a87c81033.mspx?mfr=true
I have found
"TcpWindowSize
.....
The stack also tunes itself based on the media speed:
- Below 1 Mbps: 8 KB
- 1 Mbps 100 Mbps: 17 KB
- Greater than 100 Mbps: 64 KB"
- Is this true for a WinXP professional? The tcp window size depends on the
RTT and media speed - not only media speed.
- If true, the theoretical max bandwidth is 8kB * 8 bit / 125ms = 512kbps -
never 100% of the vailable bandwidth! (In my case less because of packet loss)
- Is it possible to disable this "tuning"?
Regards, Mats