Talk:Goodput

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
WikiProject Computing / Networking (Rated Start-class, Mid-importance)
WikiProject iconThis article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
Start-Class article Start  This article has been rated as Start-Class on the project's quality scale.
 Mid  This article has been rated as Mid-importance on the project's importance scale.
Taskforce icon
This article is supported by Networking task force (marked as High-importance).
 

DrBob127 00:40, 12 September 2006 (UTC)Goodput is similar to throughput. Throughput is the rate at which a source can push packets to a sink (packets transmitted minus packets dropped). Goodput is throughput as seen from the user's perspective (packets received minus duplicate packets).

Untitled[edit]

Reference: Arora, R.M., "TCP/IP Networks with ECN over AQM", Master's Thesis, Carleton University, April 2003, Section 2.3.3 & 2.3.4DrBob127 00:40, 12 September 2006 (UTC)

Please explain how compression relates to or interacts with goodput. - mako (talkcontribs) 10:05, 12 November 2006 (UTC)

Terminology[edit]

I know wikipedia is a slave to convention (eg, using existing common terms rather than inventing it's own) but the term "goodput" sounds like an "appealing placement" rather than describing what it's actually about, such as "application level throughput"/"application layer throughput" (relating to the OSI model of network layers) or just "useful throughput". How commonly used is "goodput" really? Also the term "good" is subjective; high application layer/level throughput for malware isn't a good thing for the owner of an infected computer — Lee Carré 23:27, 7 July 2007 (UTC)

Goodput is a fairly established term in the network testing profession, but as far as I can see not widely used even amongst (regular) network professionals. The term is not for describing the content of the data (like stated above, it well could be malware), but the data which is successfully transfered (as opposed to the data in packets that are lost or mangled). Eseim (talk) 15:54, 24 September 2008 (UTC)
Every network layer adds its overhead. Goodput looks very specific to the "TCP-testing" profession. Marchash (talk) 13:40, 20 July 2009 (UTC)
'Goodput' may come from Queuing Theory. The earliest reference I've found is this 1984 abstract: the customer, unknown to the system, turns 'bad' at a random time after its arrival ... the performance of such systems is measured by the rate at which it serves good customers ('goodput'). Also, the term appears to be in declining use[1].
(Update:) Found another in a 1983 economics book: Actually, the firm's output is comprised of both "goodput" and "badput," the "goodput" being the obvious, productive output---the "badput" being that output's ill effects; pollution, accidents and illness, and so on.. - DLeonard (talk) 12:16, 24 April 2018 (UTC)

Neologism?[edit]

I always thought wikipedia had a policy against neologisms. 212.213.204.99 09:26, 9 August 2007 (UTC)

The manual of style does caution against them: http://en.wikipedia.org/wiki/Wikipedia:Avoid_neologisms#Articles_on_neologisms Merreborn (talk) 22:55, 12 January 2010 (UTC)
What? Goodput is a widespread term in the computer networkning literature. Mange01 (talk) 17:26, 23 March 2011 (UTC)
  1. ^ Google Trends https://trends.google.com/trends/explore?date=all&q=goodput. Retrieved 24 April 2018.  Missing or empty |title= (help)