|
Size: 489
Comment:
|
← Revision 6 as of 2003-12-12 20:45:29 ⇥
Size: 844
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 10: | Line 10: |
| || packet # ACKed || Congestion Window || | || packet # ACKed || Congestion Window size || |
| Line 18: | Line 18: |
| || Number of packets sent || Congestion window size || | || Number of congestion windows sent || Congestion window size || || 0 || 1 || || 1 || 2 || || 2 || 4 || || 3 || 8 || || 4 || 16 || || 5 || 32 || || 6 || 64 || ||...||...|| This continues until the MAX_TCPWIN size is reached. Since the MAX_ADVERTISED_WINDOW_SIZE = 64 KB, it doesn't make sense to allow it to grow beyond that, as you won't be able to send more than the advertised window size. |
Back to TransmissionControlProtocol
Slow start happens during several scenarios:
- When you start a connection
- When you experience a Timeout
In this initial phase we increase the congestion window for every packet that is ACKed.
packet # ACKed |
Congestion Window size |
1 |
2 |
2 |
3 |
3 |
4 |
... |
... |
The results in an exponential growth
Number of congestion windows sent |
Congestion window size |
0 |
1 |
1 |
2 |
2 |
4 |
3 |
8 |
4 |
16 |
5 |
32 |
6 |
64 |
... |
... |
This continues until the MAX_TCPWIN size is reached. Since the MAX_ADVERTISED_WINDOW_SIZE = 64 KB, it doesn't make sense to allow it to grow beyond that, as you won't be able to send more than the advertised window size.
Back to TransmissionControlProtocol