Speed
This is the most generic performance term used in
networking. As such, it can mean just about anything. Most
commonly, however, it refers to the rated or nominal speed
of a particular networking technology. For example, Fast Ethernet has a nominal
speed of 100 megabits per second; it is for that reason often called 100 Mbit
Ethernet, or given a designation such as “100BASE-TX”.
Rated speed is the biggest “performance magic number” in
networking—you see it used to label hardware devices, and many people bandy the
numbers about as if they actually were the real “speed of the network”. The
problem with using nominal speed ratings is that they are theoretical only,
and as such, tell an incomplete story. No networking technology can run at its
full rated speed, and many run substantially below
it, due to real-world
performance factors.
Speed ratings such as “100 Mbps Ethernet” are also often
referred to as the “throughput” of a technology, even though the maximum
theoretical speed of a technology is more analogous to bandwidth than
throughput, and the two are not identical. More on this in the next two bullet
points.
Bandwidth
Bandwidth is a widely-used term that usually refers to the
data-carrying capacity of a network or data transmission medium. It indicates
the maximum amount of data that can pass from one point to another in a unit of
time. The term comes from the study of electromagnetic radiation, where it
refers to the width of a band of frequencies used to carry data. It is usually
given in a theoretical context, though not always.
Bandwidth is still used in these two senses: “frequency band
width” and data capacity. For example, radio frequencies are used for wireless
technologies, and the bandwidth of such technologies can refer to how wide the
RF band is. More commonly, though, it refers to how much data can be sent down
a network, and is often used in relative terms. For example, for Internet
access, a cable or xDSL is considered “high bandwidth” access; using a regular
analog modem is “low bandwidth”.
Throughput
Throughput is a measure of how much actual data can be sent
per unit of time across a network, channel or interface. While throughput can
be a theoretical term like bandwidth, it is more often used in a practical sense,
for example, to measure the amount of data actually sent across a network in
the “real world”. Throughput is limited by bandwidth, or by rated speed: if an
Ethernet network is rated at 100 megabits per second, that's the absolute upper
limit on throughput, even though you will normally get quite a bit less. So,
you may see someone say that they are using 100 Mbps Ethernet but getting
throughput of say, 71.9 Mbps on their network.
The terms bandwidth and throughput are often used
interchangeably, even though they are really not exactly the same, as I just
discussed.
Latency
This very important, often overlooked term, refers to the timing of
data transfers on a communications channel or network. One important aspect of
latency is how long it takes from the time a request for data is made until it
starts to arrive. Another aspect is how much control a device has over the
timing of the data that is sent, and whether the network can be arranged to
allow for the consistent delivery of data over a period of time. Low latency is
considered better than high latency.
Applying Performance Measurement Terms
As with all networking terms, there are no hard and fast
rules; many people are rather loose with their use of the terms above. You will
even see terms such as “throughput bandwidth”, “bandwidth throughput” and other
charming inventions from the department of redundancy department. J More
often, you will just see a lot of mish-mashed term usage, and especially,
spurious conclusions being drawn about what data streams a network can handle
based on its rated speed. Making matters worse is that speed ratings are
usually specified in bits per second, but throughput may be given in bits or
bytes per second.
In general, “speed”, bandwidth and throughput get a lot of
attention, while latency gets little. Yet latency considerations are very
important for many real-time applications such as streaming audio and video and
interactive gaming. In fact, they are often more important than raw bandwidth.
For example, suppose you move to a rural home and your
choices for Internet access are a regular 28.8 kbps modem connection or fancy satellite
Internet. The companies selling satellite connectivity call it “broadband” and
advertise very high rated speeds—400 kbps or more. They make a big deal about
it being “over 10 times as fast as dialup” and they certainly charge a lot for
this very high-tech service. This is a slam dunk, right?
Wrong. The satellite connection has high bandwidth, but very
poor (high) latency due to the time it takes for the signals to travel to and
from the satellite. It is definitely much better than the modem for downloading
that nice little 150 MB patch from Microsoft. However, it is much worse than
the modem for playing the latest online video game with your buddy over the
Internet, because of the latency, or lag, in transmissions. Every
move you make in your game will be delayed for over half a second as the signal
bounces around between the satellite and the earth, making online gaming nearly
impossible. Thus, whether satellite Internet is worth the extra money depends
entirely on what you plan to use it for.
No comments:
Post a Comment