You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Modify the routing table to force all the traffic being sending to IP1 go via the NIC configured with IP2.
By following the above steps, the latency graph would contain the time spent between udpsink and udpsrc. But before trying the whole process, I first tried to profile this pipeline without modifying the routing table, which means, the time spent between udpsink and udpsrc is negligible. However, the resulting latency graph looks like the following:
The lines intersect with each other. But they shouldn't if things went well. It seems that the time a frame reaches udpsrc is reset to 0. I was wondering if it is because of the limitation of gst-shark interlatency plugin, or if there is something missing in the pipeline description. Looking forward to any hints or solutions!
The text was updated successfully, but these errors were encountered:
I want to measure the latency incurred by the network. I came up with the following method:
Install two network interfaces on the same host, suppose they get IP1 and IP2;
Run gst-shark interlatency, with the following command:
By following the above steps, the latency graph would contain the time spent between udpsink and udpsrc. But before trying the whole process, I first tried to profile this pipeline without modifying the routing table, which means, the time spent between udpsink and udpsrc is negligible. However, the resulting latency graph looks like the following:
The lines intersect with each other. But they shouldn't if things went well. It seems that the time a frame reaches udpsrc is reset to 0. I was wondering if it is because of the limitation of gst-shark interlatency plugin, or if there is something missing in the pipeline description. Looking forward to any hints or solutions!
The text was updated successfully, but these errors were encountered: