...
We have already created the network namespace environment needed to run both iPerf3 Client and Server on the same host, and ensure that traffic follows the external path as shown below.
IPerf 3 was sending at low packet rates (~40K pps) in initial testing - this means we are only capturing BIG interrupts with this stream.
With DPDK operating at higher rates, and buffer size set on per packet basis - will fill the buffers more easily.
T-rex core occupation = 4 in current configurations.
URL to PROX tool, which can examine interrupt effects on a heartbeat on each core: https://github.com/opnfv/samplevnf/tree/master/VNFs/DPPD-PROX/
Related papers:
https://www.net.in.tum.de/fileadmin/bibtex/publications/papers/SPECTS15NAPIoptimization.pdf
https://www.net.in.tum.de/fileadmin/bibtex/publications/papers/NetSys2015.pdf
As an example of the iPerf3 loss counting capability, we have the results of one 60 second test below (where each second would be a trial):
...