Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

IPerf 3 was sending at low packet rates (~40K pps) in initial testing - this means we are only capturing BIG interrupts with this stream (see sample output below).

With DPDK operating at higher rates, and buffer size set on per packet basis - will fill the buffers more easily.

T-rex core occupation assignment = 4 cores 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

Image Removed

This is PROX output, where PROX snapshot output for VSPERF Intel Pod 12, Node 4 (the Device Under Test, DUT, for the Long Duration and Cross-NUMA Node testing).

Image Added

In this PROX output, it is clear that something is producing interrupts in the xxx range on core 6.

We can get these statistics on a per-second basis, from a TCP socket - there is syntax to request these stats.  (also -k command, Xavier will share scripts which are better).

...

[  5]   0.00-60.04  sec  0.00 Bytes  0.00 bits/sec  0.004 ms  273/2586968 (0.011%)


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