♦ What causes the network traffic to emerge from hosts in bursts?
♦ Is burstiness an scale-invariant property of traffic? (Does the traffic retain its burstiness across a wide range of timescales, or do the
microbursts become smooth at coarse timescales?)
♦ Are canonical burst countermeasures such as TCP pacing and packet scheduling effective in curtailing bursts?
Our study attempts to find an answer for above questions.
Valinor framework offers visibility into traffic burstiness over a wide span of timescales (nanosecond- to second-scale) at multiple vantage points by capturing timestamp and metadata information for incoming/outgoing packets in the network.
Valinor consists of four components:
Example deployment scenario:
TCP congestion control variants use different signals to detect congestion in the network. This results in significantly different buffer utilization patterns. Valinor-N can capture the dynamics of switch buffer utilization
at microsecond granularity.
Linux offers a modular platform for implementing various packet scheduling paradigms, called queueing disciplines or in short, qdiscs.
However, are these software elements effecting in shaping the traffic when NIC segmentation offloading and lulti-ring scheduling functions are active?
We compare two Linux qdiscs, fq and pfifo_fast under four configurations. Our results suggest that low layers of the network stack compromise the traffic shaping efforts of the software packet schedulers:
More interesting results on impact of TCP pacing, Linux qdiscs, and process scheduling on packet bursts can be found in our published paper.
The publication can be access at NSDI '23 website.
The super repository containing Valinor artifacts can be found here!.
Please email the authors with your questions and ideas on improving Valinor.