4 ms·
Sure, tc can be used for adding a fixed delay (or random delay that follows a given distribution) to network traffic. In the use case that prompted me to develo
by kffl 4y ago
Sure, tc can be used for adding a fixed delay (or random delay that follows a given distribution) to network traffic. In the use case that prompted me to develop speedbump (testing application metrics collection and visualization), I wanted to achieve artificial latency being added value of which would change predictably over time (i.e. forming a sawtooth wave or a sine wave so as to give me immediate visual feedback when testing/debugging PromQL queries visualized in Grafana dashboards), which I don't think is possible to achieve with tc alone.
On top of that, I usually work on metrics collection, visualization and load testing in a staging k8s cluster, in which it would be rather tedious to set up tc rules on the worker nodes themselves (or even impossible in the case of managed K8s services with no direct access to the VMs acting as worker nodes).
- majke 4y ago> which I don't think is possible to achieve with tc alone. How you do it with tc: - set up dedicated network namespacel, with veth configured well - the veth on host should do forwarding and NAT/masquerade - Add TC either on veth inside ns or veth on host, or both (depending on direction you want to add latency) - then wait - then change the tc parameters if you want the parameters to change Now, the big problem with tc netem variable latency is that it does reorder packets, which is often undesirable. So, if your project does _not_ effect in packet reorder, it could be useful. Having said that, it seems to focus on L7 layer which is slightly too high level for the stuff I 'm doing. Anyway, nice tool.
- deleted 4y ago[deleted]