Goodput

From Wikipedia, the free encyclopedia

In computer networks and wireless networks, goodput is the application level throughput, i.e. the number of useful bits per unit of time forwarded by the network from a certain source address to a certain destination, excluding protocol overhead, and excluding retransmitted data packets.

For example, if a file is transferred, the goodput that the user experiences corresponds to the file size in bits divided by the file transfer time. The goodput is generally lower than the throughput (the gross bit rate that is transferred physically), which generally is lower than network access connection speed (the channel capacity or digital bandwidth).

Examples of factors that may cause lower goodput than throughput are:

  • Protocol overhead.
  • Retransmission of lost or corrupt packets, caused by bit errors or packet dropping in congested switches and routers. Automatic repeat request (ARQ), i.e. retransmission of lost or corrupt data packets, is supported by the TCP protocol, some UDP based application layer protocols, and by reliable data link layer protocol used for example in wireless networks.
  • Collision detection in the Ethernet CSMA/CD protocol, and collision avoidance in for example wireless local area networks using the CSMA/CA protocol, may cause "backoff" waiting time (i.e. increased interframe gap) and retransmission.

Imagine that a file is being transferred using HTTP over a switched ethernet connection with a total channel capacity of 100 megabits per second. The file cannot be transferred over ethernet as a single contiguous stream, instead it must be broken down into individual segments, called packets. These packets must be no larger than the maximum transmission unit of ethernet, which is 1500 bytes. Each packet requires 20 bytes of IP header information and 20 bytes of TCP header information, so only 1460 bytes are available per packet for the file transfer data itself. Furthermore, the packets are transmitted over ethernet in a frame which imposes a 38 byte overhead per packet. Given these overheads, the maximum goodput is \frac{1460}{1538} \cdot 100 Mbit/s which is 94.92 megabits per second or 11.866 megabytes per second.

  1. Goodput calculation
  2. An Empirical Characterization of Instantaneous Throughput in 802.11b WLANs
  3. Energy-Efficient Power and Rate Control with QoS Constraints: A Game-Theoretic Approach
  4. Benchmarking Terminology for Firewall Performance


Advanced Search
Included Web Search Engines


Safe Search

close

Top Matching Results

Occasionally Search.com will highlight specialized results that are based on the context of your query. Examples of specialized results include specific links to news, images, or video.

Top Matching Results may highlight information from other Search.com pages, content from the CNET Network of sites, or third party content. The listings are based purely on relevance. Search.com does not receive payment for listings in this section but our partners that provide this data may get paid for listing these products.

Sponsored Links

This section contains paid listings which have been purchased by companies that want to have their sites appear for specific search terms and related content. These listings are administered, sorted and maintained by a third party and are not endorsed by Search.com.

Search Results

Search.com sends your search query to several search engines at one time and integrates the results into one list which has been sorted by relevance using Search.com's proprietary algorithm. You can customize the list of search engines included in your metasearch from the preferences.

The search engines that are used in your metasearch may allow companies to pay to have their Web sites included within the results. To view the Paid Inclusion policy for a specific search engine, please visit their Web site. Search.com does not accept payment or share revenue with any search engine partner for listings in this section.