MétaCan
Menu
Back to cohort
Record W2505795549 · doi:10.1504/ijcnds.2016.077939

Comparative performance analysis of TCP-based congestion control algorithms

2016· article· en· W2505795549 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

fundA Canadian funder is recorded on the work.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueInternational Journal of Communication Networks and Distributed Systems · 2016
Typearticle
Languageen
FieldComputer Science
TopicNetwork Traffic and Congestion Control
Canadian institutionsnot available
FundersCanadian Centre for Applied Research in Cancer Control
KeywordsComputer scienceTCP Friendly Rate ControlTCP global synchronizationTCP Westwood plusTCP tuningTCP accelerationCUBIC TCPH-TCPZeta-TCPComputer networkAlgorithmNetwork congestionGoodputThroughputNetwork packetWirelessTelecommunications

Abstract

fetched live from OpenAlex

Congestion control is a challenging problem for us. We tried to analyse the end-to-end congestion control algorithms, i.e., TCP Tahoe, TCP Reno, TCP Newreno, TCP Veno, etc. In the literature, TCP implements a window-based flow control mechanism which leads to vary the window size within a range. Older TCP designed assuming packet loss is always inferred due to congestion on link which leads to degradation of performance in wireless networks where random loss occurred due to transmission error or noise. This well-known problem affects on TCP performance. TCP Veno has been successfully proposed to deal with random loss efficiently and its performance is discussed in the literature. This paper evaluates the complex model for different performance parameters, i.e., throughput, queuing delay, goodput, etc. In addition, we have also proposed new performance metric to measure the network performance. We also tried to study and compare the analytical results with simulated data at different levels of loss rate.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.968
Threshold uncertainty score0.343

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.015
GPT teacher head0.259
Teacher spread0.244 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it