|
|
| Line 1: |
Line 1: |
| {{IPstack}}
| | Alyson is what my spouse loves to call me but I don't like when people use my complete title. My husband doesn't like it the way I do but what psychic chat online ([http://breenq.com/index.php?do=/profile-1144/info/ please click the next web page]) I really like performing is caving but I don't have the time lately. I've always loved living in Kentucky but now I'm contemplating other choices. Since I was 18 I've been working as a bookkeeper but soon my wife and I [http://isaworld.pe.kr/?document_srl=392088 love psychic] will start our personal company.<br><br>Feel free to visit my site - email psychic readings ([http://www.youronlinepublishers.com/authWiki/AdolphvhBladenqq linked internet page]) |
| | |
| '''TCP tuning''' techniques adjust the [[network congestion avoidance]] parameters of [[Transmission Control Protocol|TCP]] connections over high-bandwidth, high-latency networks. Well-tuned networks can perform up to 10 times faster in some cases.<ref>[http://www.psc.edu/networking/projects/hpn-ssh/ High Performance Enabled SSH/SCP [PSC]<!-- Bot generated title -->]</ref> However, blindly following instructions without understanding their real consequences can hurt the performance as well. | |
| | |
| == Network and system characteristics == | |
| === Bandwidth-delay product (BDP) ===
| |
| | |
| [[Bandwidth-delay product]] (BDP) is a term primarily used in conjunction with the [[Transmission control protocol|TCP]] to refer to the number of bytes necessary to fill a TCP "path", i.e. it is equal to the maximum number of simultaneous bits in transit between the transmitter and the receiver.
| |
| | |
| High performance networks have very large BDPs. To give a practical example, two nodes communicating over a geostationary satellite link with a round trip delay of 0.5 seconds and a bandwidth of 10 Gbit/s can have up to 0.5×10<sup>10</sup> bits, i.e., 5 Gbit = 625 [[megabyte|MB]] of unacknowledged data in flight. Despite having much lower latencies than satellite links, even terrestrial fiber links can have very high BDPs because their link capacity is so large. Operating systems and protocols designed as recently as a few years ago when networks were slower were tuned for BDPs of orders of magnitude smaller, with implications for limited achievable performance.
| |
| | |
| === Buffers ===
| |
| The original TCP configurations supported [[Buffer (computer science)|buffer]]s of up to 65,535 Bytes (64 [[kibibyte|KiB]]-1) ''TCP receive window size'', which was adequate for slow links or links with small round trip times (RTTs). Larger buffers are required by the high performance options described below.
| |
| | |
| Buffering is used throughout high performance network systems to handle delays in the system. In general, buffer size will need to be scaled proportionally to the amount of data "in flight" at any time. For very high performance applications that are not sensitive to network delays, it is possible to interpose large end to end buffering delays by putting in intermediate data storage points in an end to end system, and then to use automated and scheduled non-real-time data transfers to get the data to their final endpoints.
| |
| | |
| == TCP speed limits ==
| |
| Maximum achievable throughput for a single TCP connection is determined by different factors. One trivial limitation is the maximum bandwidth of the slowest link in the path. But there are also other, less obvious limits for TCP throughput. Bit errors can create a limitation for the connection as well as [[round-trip time]].
| |
| | |
| === Window size ===<!--[[Receive Window]] redirects here-->
| |
| {{see also|TCP window scale option|Congestion window}}
| |
| | |
| In [[computer networking]], '''RWIN''' ([[Transmission Control Protocol|TCP]] Receive Window) is the amount of [[Data (computing)|data]] that a [[computer]] can accept without acknowledging the sender. If the sender has not received acknowledgement for the first [[packet (information technology)|packet]] it sent, it will stop and wait and if this wait exceeds a certain limit, it may even [[Retransmission (data networks)|retransmit]]. This is how TCP achieves reliable [[data transmission]].
| |
| | |
| Even if there is no packet loss in the network, [[Tcp receive window|windowing]] can limit throughput. Because TCP transmits data up to the window size before waiting for the acknowledgements, the full bandwidth of the network may not always get used. The limitation caused by window size can be calculated as follows:
| |
| | |
| <math> \mathrm{Throughput} \le \frac {\mathrm{RWIN}} {\mathrm{RTT}} \,\!</math> <!-- The \,\! is to keep the formula rendered as PNG instead of HTML. Please don't remove it. It matches the next formula. -->
| |
| | |
| where RWIN is the TCP Receive Window and RTT is the [[Round-trip delay time|round-trip time]] for the path.
| |
| | |
| At any given time, the window advertised by the receive side of TCP corresponds to the amount of free receive memory it has allocated for this connection. Otherwise it would risk dropping received packets due to lack of space.
| |
| | |
| The sending side should ''also'' allocate the same amount of memory as the receive side for good performance. That is because, even after data has been sent on the network, the sending side must hold it in memory until it has been acknowledged as successfully received, just in case it would have to be retransmitted. If the receiver is far away, acknowledgments will take a long time to arrive. If the send memory is small, it can saturate and block emission. A simple computation gives the same optimal send memory size as for the receive memory size given above.
| |
| | |
| === Packet loss ===
| |
| When packet loss occurs in the network, an additional limit is imposed on the connection.<ref>http://www.psc.edu/networking/papers/model_ccr97.ps</ref> In the case of light to moderate packet loss when the TCP rate is limited by the [[TCP congestion avoidance algorithm|congestion avoidance algorithm]], the limit can be calculated according to the formula (Mathis et al.):
| |
| | |
| <math> \mathrm{Throughput} \le \frac {\mathrm{MSS}} {\mathrm{RTT} \sqrt{ P_{\mathrm{loss} }}}</math> | |
| | |
| where MSS is the maximum segment size and ''P''<sub>loss</sub> is the probability of packet loss.<ref>RFC 3155</ref> If packet loss is so rare that the TCP window becomes regularly fully extended, this formula doesn't apply.
| |
| | |
| ==TCP Options for High Performance==
| |
| | |
| A number of extensions have been made to TCP over the years to increase its performance over fast high-RTT links ("long fat networks", or LFNs for short).
| |
| | |
| TCP timestamps (RFC 1323) play a double role: they avoid ambiguities due to the 32-bit sequence number field wrapping around, and they allow more precise RTT estimation in the presence of multiple losses per RTT. With those improvements, it becomes reasonable to increase the TCP window beyond 64 kB, which can be done using the window scaling option (RFC 1323).
| |
| | |
| The TCP selective acknowledgment options (SACK, RFC 2018) allows a TCP receiver to precisely inform the TCP server about which segments have been lost. This increases performance on high-RTT links, when multiple losses per window are possible.
| |
| | |
| [[Path MTU discovery]] avoids the need for in-network fragmentation, which increases performance in the presence of losses.
| |
| | |
| == References ==
| |
| <references />
| |
| | |
| == External links ==
| |
| * RFC 1323 - TCP Extensions for High Performance
| |
| * RFC 2018 - TCP Selective Acknowledgment Options
| |
| * RFC 2582 - The NewReno Modification to TCP's Fast Recovery Algorithm
| |
| * RFC 2883 - An Extension to the Selective Acknowledgment (SACK) Option for TCP
| |
| * RFC 3517 - A Conservative Selective Acknowledgment-based Loss Recovery Algorithm for TCP
| |
| * RFC 4138 - Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP and the Stream Control Transmission Protocol (SCTP)
| |
| * [http://fasterdata.es.net/TCP-tuning/background.html TCP Tuning Guide], ESnet
| |
| * [http://www.microsoft.com/technet/technetmag/issues/2007/01/CableGuy/default.aspx The Cable Guy: TCP Receive Window Auto-Tuning]
| |
| * [http://www.web100.org/ The Web100 Data Bandwidth Testing]
| |
| * [http://www.dslreports.com/drtcp DrTCP] - a utility for [[Microsoft Windows]] (prior to [[Windows Vista|Vista]]) which can quickly alter [[Transmission Control Protocol|TCP]] performance parameters in the registry.
| |
| * [http://www.dslreports.com/tweaks Information on 'Tweaking' your TCP stack], [[Broadband Reports]]
| |
| * [http://www.speedguide.net/analyzer.php TCP/IP Analyzer], speedguide.net
| |
| * [http://blogs.technet.com/winserverperformance/archive/2008/05/03/nt-ttcp-network-performance-test-tool-available.aspx NTTTCP Network Performance Test Tool], Microsoft Windows Server Performance Team Blog
| |
| | |
| [[Category:Transmission Control Protocol|Tuning]]
| |
| [[Category:Network performance]]
| |
Alyson is what my spouse loves to call me but I don't like when people use my complete title. My husband doesn't like it the way I do but what psychic chat online (please click the next web page) I really like performing is caving but I don't have the time lately. I've always loved living in Kentucky but now I'm contemplating other choices. Since I was 18 I've been working as a bookkeeper but soon my wife and I love psychic will start our personal company.
Feel free to visit my site - email psychic readings (linked internet page)