Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Network performance
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{short description|Network service quality}} '''Network performance''' refers to measures of [[service quality]] of a network as seen by the customer. There are many different ways to measure the performance of a network, as each network is different in nature and design. Performance can also be modeled and simulated instead of measured; one example of this is using state transition diagrams to model queuing performance or to use a Network Simulator. ==Performance measures== The following measures are often considered important: * '''Bandwidth''' commonly measured in bits/second is the maximum rate that information can be transferred * '''Throughput''' is the actual rate that information is transferred * '''Latency''' the delay between the sender and the receiver decoding it, this is mainly a function of the signals travel time, and processing time at any nodes the information traverses * '''Jitter''' variation in packet delay at the receiver of the information * '''Error rate''' the number of corrupted bits expressed as a percentage or fraction of the total sent ===Bandwidth=== {{Main|Bandwidth (computing)}} The available channel bandwidth and achievable signal-to-noise ratio determine the maximum possible throughput. It is not generally possible to send more data than dictated by the [[Shannon-Hartley Theorem]]. ===Throughput=== {{Main|Throughput}} ''Throughput'' is the number of messages successfully delivered per unit time. Throughput is controlled by available bandwidth, as well as the available signal-to-noise ratio and hardware limitations. Throughput for the purpose of this article will be understood to be measured from the arrival of the first bit of data at the receiver, to decouple the concept of throughput from the concept of latency. For discussions of this type, the terms 'throughput' and 'bandwidth' are often used interchangeably. The ''Time Window'' is the period over which the throughput is measured. The choice of an appropriate time window will often dominate calculations of throughput, and whether latency is taken into account or not will determine whether the latency affects the throughput or not. ===Latency=== {{Main|Latency (engineering)}} The [[speed of light]] imposes a minimum propagation time on all electromagnetic signals. It is not possible to reduce the latency below :<math>t=s/c_m</math> where s is the distance and c<sub>m</sub> is the speed of light in the medium (roughly 200,000 km/s for most [[optical fiber|fiber]] or [[electrical cable|electrical]] media, depending on their [[velocity factor]]). This approximately means an additional millisecond [[round-trip delay]] (RTT) per 100 km (or 62 miles) of distance between hosts. Other delays also occur in intermediate nodes. In packet switched networks delays can occur due to queueing. ===Jitter=== {{Main|Jitter}} '''Jitter''' is the undesired deviation from true periodicity of an assumed periodic [[signal]] in [[electronics]] and [[telecommunications]], often in relation to a reference [[clock signal|clock source]]. Jitter may be observed in characteristics such as the [[frequency]] of successive pulses, the signal [[amplitude]], or [[phase (waves)|phase]] of periodic signals. Jitter is a significant, and usually undesired, factor in the design of almost all communications links (e.g., [[USB]], [[PCI-e]], [[SATA]], [[OC-48]]). In [[clock recovery]] applications it is called ''timing jitter''.<ref name=wol91p211>[[#Wol1991|Wolaver, 1991, p.211]]</ref> ===Error rate=== {{Main|Bit error rate}} In [[digital transmission]], the number of '''bit errors''' is the number of received [[bit]]s of a [[data stream]] over a [[communication channel]] that have been altered due to [[noise (telecommunications)|noise]], [[interference (communication)|interference]], [[distortion]] or [[bit synchronization]] errors. The '''bit error rate''' or '''bit error ratio''' ('''BER''') is the number of bit errors divided by the total number of transferred bits during a studied time interval. BER is a unitless performance measure, often expressed as a [[percentage]]. The '''bit error probability''' ''p<sub>e</sub>'' is the [[expectation value]] of the BER. The BER can be considered as an approximate estimate of the bit error probability. This estimate is accurate for a long time interval and a high number of bit errors. ===Interplay of factors=== All of the factors above, coupled with user requirements and user perceptions, play a role in determining the perceived 'fastness' or utility, of a network connection. The relationship between throughput, latency, and user experience is most aptly understood in the context of a shared network medium, and as a scheduling problem. ==Algorithms and protocols== For some systems, latency and throughput are coupled entities. In TCP/IP, latency can also directly affect throughput. In [[Transmission Control Protocol|TCP]] connections, the large [[bandwidth-delay product]] of high latency connections, combined with relatively small TCP window sizes on many devices, effectively causes the throughput of a high latency connection to drop sharply with latency. This can be remedied with various techniques, such as increasing the TCP congestion window size, or more drastic solutions, such as packet coalescing, [[TCP acceleration]], and [[forward error correction]], all of which are commonly used for high latency satellite links. TCP acceleration converts the TCP packets into a stream that is similar to [[User Datagram Protocol|UDP]]. Because of this, the TCP acceleration software must provide its own mechanisms to ensure the reliability of the link, taking the latency and bandwidth of the link into account, and both ends of the high latency link must support the method used. In the Media Access Control (MAC) layer, performance issues such as throughput and end-to-end delay are also addressed. ==Examples of latency or throughput dominated systems== Many systems can be characterized as dominated either by throughput limitations or by latency limitations in terms of end-user utility or experience. In some cases, hard limits such as the speed of light present unique problems to such systems and nothing can be done to correct this. Other systems allow for significant balancing and optimization for best user experience. ===Satellite=== A telecom satellite in geosynchronous orbit imposes a path length of at least 71000 km between transmitter and receiver.<ref>Roddy, 2001, 67 - 90</ref> which means a minimum delay between message request and message receipt, or latency of 473 ms. This delay can be very noticeable and affects satellite phone service regardless of available throughput capacity. ===Deep space communication=== These long path length considerations are exacerbated when communicating with space probes and other long-range targets beyond Earth's atmosphere. The [[Deep Space Network]] implemented by NASA is one such system that must cope with these problems. Largely latency driven, the GAO has criticized the current architecture.<ref>U.S. Government Accounting Office (GAO), 2006</ref> Several different methods have been proposed to handle the intermittent connectivity and long delays between packets, such as [[delay-tolerant networking]].<ref>Kevin Fall, 2003</ref> ===Even deeper space communication=== At interstellar distances, the difficulties in designing radio systems that can achieve any throughput at all are massive. In these cases, maintaining communication is a bigger issue than how long that communication takes. ===Offline data transport=== Transportation is concerned almost entirely with throughput, which is why physical deliveries of backup tape archives are still largely done by vehicle. == See also == * [[Bitrate]] * [[Measuring network throughput]] * [[Network traffic measurement]] * [[Round-trip delay time|Response time]] ==Notes== {{Reflist}} == References == * {{cite book|last=Rappaport|first=Theodore S.|title=Wireless communications : principles and practice|year=2002|publisher=Prentice Hall PTR|location=Upper Saddle River, NJ|isbn=0-13-042232-0|edition=2}} * {{cite book|last=Roddy|first=Dennis|title=Satellite communications|year=2001|publisher=McGraw-Hill|location=New York [u.a.]|isbn=0-07-137176-1|edition=3.}} * Fall, Kevin, [https://web.archive.org/web/20110724161930/http://www.dtnrg.org/docs/papers/IRB-TR-03-003.pdf "A Delay-Tolerant Network Architecture for Challenged Internets"], Intel Corporation, February, 2003, Doc No: IRB-TR-03-003 *Government Accountability Office (GAO) report 06-445, NASA'S DEEP SPACE NETWORK: Current Management Structure is Not Conducive to Effectively Matching Resources with Future Requirements, April 27, 2006 == External links == * [https://web.archive.org/web/20120608040231/http://deepspace.jpl.nasa.gov/dsn/ NASA's Deep Space Network Website] * "[https://web.archive.org/web/20141204094820/http://www.stuartcheshire.org/rants/Latency.html It's the Latency, Stupid]" {{Computer science}} {{Authority control}} [[Category:Network performance| ]] [[Category:Computing comparisons]] [[Category:Information theory]]
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)
Pages transcluded onto the current version of this page
(
help
)
:
Template:Authority control
(
edit
)
Template:Cite book
(
edit
)
Template:Computer science
(
edit
)
Template:Main
(
edit
)
Template:Reflist
(
edit
)
Template:Short description
(
edit
)