How to apportion blame for a queue with arrivals in different bursts?
Comparison of different ECN marking algorithms applied to two unresponsive flows with different burst amplitudes and different regular intervals between bursts. See the overview presentation of the results (below) for explanation and justification of the approach.
- Overview: "How to Apportion Blame for a Queue with Arrivals in Bursts?"
- Detailed results "Signalling Bursty Queue Delay; Expt 1.1" using one of a choice of four metrics:
- The technical report on this research: "Rapid Signalling of Queue Dynamics"
[ Latest work-in-progress version | Latest published version ]
(neither are necessarily as up to date as the Overview presentation above).
To repeat the experiments:
- Edit primary and secondary parameters directly in the file
blameshift_unresp.mand save. - Run either from within octave as
>> blameshift_unresp
or from the command line as
$ octave blameshift_unresp.m - A binary (.bin) file of the results is saved at the end, in subdirectory
octave_dataif it exists, otherwise in the current directory. - To plot output at any time, this saved binary can be loaded into octave:
>> load <file.bin>
But this is unnecessary if plotting is done immediately after running this script, while the output is still in memory. - Then a second script must be run from octave, depending on how
qt_modewas set in the original script:
>> blameshift_unresp_plot_qt# time series plot (requiresqt_mode = true(1))
>> blameshift_unresp_plot_stats# 2-D plot of parameter space (requiresqt_mode = false(1))
>> blameshift_unresp_mesh_stats# 3-D plot of parameter space (requiresqt_mode = false(1))
See the source of each of these scripts for their usage.
- octave 5.2.0 under Ubuntu 20.04 LTS
- octave 7.3.0 under Win 10
Not tested from MatLab