4 Changes in CSIT |release|
5 -------------------------
9 - new NICs - Intel x520
11 Multi-Thread and Multi-Core Measurements
12 ----------------------------------------
14 **HyperThreading** - CSIT |release| performance tests are executed with SUT
15 servers' Intel XEON CPUs configured in HyperThreading Disabled mode (BIOS
16 settings). This is the simplest configuration used to establish baseline
17 single-thread single-core SW packet processing and forwarding performance.
18 Subsequent releases of CSIT will add performance tests with Intel
19 HyperThreading Enabled (requires BIOS settings change and hard reboot).
21 **Multi-core Test** - CSIT |release| multi-core tests are executed in the
22 following Testpmd thread and core configurations:
24 #. 1t1c - 1 Testpmd pmd thread on 1 CPU physical core.
25 #. 2t2c - 2 Testpmd pmd threads on 2 CPU physical cores.
26 #. 4t4c - 4 Testpmd pmd threads on 4 CPU physical cores.
28 Note that in many tests running Testpmd reaches tested NIC I/O bandwidth
29 or packets-per-second limit.
31 Packet Throughput Measurements
32 ------------------------------
34 Following values are measured and reported for packet throughput tests:
36 - NDR binary search per RFC2544:
38 - Packet rate: "RATE: <aggregate packet rate in packets-per-second> pps
39 (2x <per direction packets-per-second>)"
40 - Aggregate bandwidth: "BANDWIDTH: <aggregate bandwidth in Gigabits per
41 second> Gbps (untagged)"
43 - PDR binary search per RFC2544:
45 - Packet rate: "RATE: <aggregate packet rate in packets-per-second> pps (2x
46 <per direction packets-per-second>)"
47 - Aggregate bandwidth: "BANDWIDTH: <aggregate bandwidth in Gigabits per
48 second> Gbps (untagged)"
49 - Packet loss tolerance: "LOSS_ACCEPTANCE <accepted percentage of packets
52 - NDR and PDR are measured for the following L2 frame sizes:
54 - IPv4: 64B, 1518B, 9000B.
57 Packet Latency Measurements
58 ---------------------------
60 TRex Traffic Generator (TG) is used for measuring latency of Testpmd DUTs.
61 Reported latency values are measured using following methodology:
63 - Latency tests are performed at 10%, 50% of discovered NDR rate (non drop rate)
64 for each NDR throughput test and packet size (except IMIX).
65 - TG sends dedicated latency streams, one per direction, each at the rate of
66 10kpps at the prescribed packet size; these are sent in addition to the main
68 - TG reports min/avg/max latency values per stream direction, hence two sets
69 of latency values are reported per test case; future release of TRex is
70 expected to report latency percentiles.
71 - Reported latency values are aggregate across two SUTs due to three node
72 topology used for all performance tests; for per SUT latency, reported value
73 should be divided by two.
74 - 1usec is the measurement accuracy advertised by TRex TG for the setup used in
75 FD.io labs used by CSIT project.
76 - TRex setup introduces an always-on error of about 2*2usec per latency flow -
77 additonal Tx/Rx interface latency induced by TRex SW writing and reading
78 packet timestamps on CPU cores without HW acceleration on NICs closer to the
82 Report Addendum Tests - Additional NICs
83 ---------------------------------------
85 Adding test cases with more NIC types. Once the results become available, they
86 will be published as an addendum to the current version of CSIT |release|