Difference between revisions of "CSIT/PerfTestPlan"

From fd.io
Jump to: navigation, search
Line 2: Line 2:
 
==CSIT Jenkins Jobs for Performance Tests==
 
==CSIT Jenkins Jobs for Performance Tests==
  
−
# task: verify vpp code changes as they come - performance short tests
+
{| class="wikitable"
−
#* job: [https://jenkins.fd.io/view/vpp/job/vpp-csit-verify-hw-perf-master-short/ vpp-csit-verify-hw-perf-master-short]
+
|+Jenkins Jobs
−
#* triggers: "verify-perf-short" patch comment
+
|-
−
#* vpp code: vpp master branch PLUS gerrit change under test
+
|Task
−
#* csit code: csit-verified-tag
+
|Job
−
#* testbed: LF HW compute nodes - hw-tb1,tb2,tb3
+
|Triggers (patch comment
−
#* status: WORKING
+
|VPP code
−
# task: verify vpp code changes as they come - performance long tests
+
|CSIT code
−
#* job: [https://jenkins.fd.io/view/vpp/job/vpp-csit-verify-hw-perf-master-long/ vpp-csit-verify-hw-perf-master-long]
+
|LF Testbed
−
#* triggers: "verify-perf-long" patch comment
+
|Status
−
#* vpp code: vpp master branch PLUS gerrit change under test
+
|-
−
#* csit code: csit-verified-tag
+
|Verify VPP code changes as they come - performance short tests
−
#* testbed: LF HW compute nodes - hw-tb1,tb2,tb3
+
|[https://jenkins.fd.io/view/vpp/job/vpp-csit-verify-hw-perf-master-short/ vpp-csit-verify-hw-perf-master-short]
−
#* status: WORKING
+
|"verify-perf-short"
−
# task: verify vpp code changes as they come - performance all tests
+
|VPP master branch + gerrit change under test
−
#* job: [https://jenkins.fd.io/view/vpp/job/vpp-csit-verify-hw-perf-master-all/ vvpp-csit-verify-hw-perf-master-all]
+
|csit-verified-tag
−
#* triggers: "verify-perf-all" patch comment
+
|TB1, TB2, TB3
−
#* vpp code: vpp master branch PLUS gerrit change under test
+
|WORKING
−
#* csit code: csit-verified-tag
+
|-
−
#* testbed: LF HW compute nodes - hw-tb1,tb2,tb3
+
|Verify VPP code changes as they come - performance long tests
−
#* status: WORKING
+
|[https://jenkins.fd.io/view/vpp/job/vpp-csit-verify-hw-perf-master-long/ vpp-csit-verify-hw-perf-master-long]
−
# task: verify csit code changes as they come - performance tests
+
|"verify-perf-long"
−
#* job: [https://jenkins.fd.io/view/csit/job/csit-vpp-perf-hw-all/ csit-vpp-perf-hw-all]
+
|VPP master branch + gerrit change under test
−
#* triggers: gerrit change commit, "recheck" patch comment
+
|csit-verified-tag
−
#* vpp code: vpp-master-verified vpp build
+
|TB1, TB2, TB3
−
#* csit code: csit master branch PLUS gerrit change
+
|WORKING
−
#* testbed: LF HW compute nodes - hw-tb1,tb2,tb3
+
|-
−
#* status: WORKING
+
|Verify VPP code changes as they come - all performance tests
 +
|[https://jenkins.fd.io/view/vpp/job/vpp-csit-verify-hw-perf-master-all/ vpp-csit-verify-hw-perf-master-all]
 +
|"verify-perf-all"
 +
|VPP master branch + gerrit change under test
 +
|csit-verified-tag
 +
|TB1, TB2, TB3
 +
|WORKING
 +
|-
 +
|Verify CSIT code changes as they come - all performance tests
 +
|[https://jenkins.fd.io/view/csit/job/csit-vpp-perf-master-all/ csit-vpp-perf-master-all]
 +
|"verify-perf-all"
 +
|vpp-master-verified vpp build
 +
|csit master branch + gerrit change under test
 +
|TB1, TB2, TB3
 +
|WORKING
 +
|-
 +
|Verify CSIT code changes as they come - performance long tests
 +
|[https://jenkins.fd.io/view/csit/job/csit-vpp-perf-master-long/ csit-vpp-perf-master-long]
 +
|"verify-perf-long"
 +
|vpp-master-verified vpp build
 +
|csit master branch + gerrit change under test
 +
|TB1, TB2, TB3
 +
|WORKING
 +
|-
 +
|Verify CSIT code against VPP release 16.06 - all performance tests
 +
|[https://jenkins.fd.io/view/csit/job/csit-vpp-perf-1606-all/ csit-vpp-perf-1606-all]
 +
|"verify-perf-all"
 +
|vpp-master-verified vpp build
 +
|csit stable/1606 branch
 +
|TB1, TB2, TB3
 +
|WORKING
 +
|-
 +
|Verify CSIT code against VPP release 16.06 - performance long tests
 +
|[https://jenkins.fd.io/view/csit/job/csit-vpp-perf-1606-long/ csit-vpp-perf-1606-long]
 +
|"verify-perf-long"
 +
|vpp-master-verified vpp build
 +
|csit stable/1606 branch
 +
|TB1, TB2, TB3
 +
|WORKING
 +
|}
  
 
==Performance Test Cases - Working==
 
==Performance Test Cases - Working==
  
−
# All 3 LF physical testbeds are all live - hw-tb1,tb2,tb3.
+
All 3 LF physical testbeds are all live - [https://wiki.fd.io/view/CSIT/CSIT_LF_testbed CSIT/CSIT LF testbed]
−
# Performance test cases - 56 working in FD.io physical testbeds today.
+
 
−
# List of working performance test cases
+
===CSIT test suite list for VPP v16.06===
−
#* ~/csit$ grep "^| [a-zA-Z1-9]" -nr tests | grep -vi " | "  | sort | grep performance
+
 
−
## tests/suites/performance/Long_Bridge_Domain_Intel-X520-DA2.robot:123:| Find NDR by using RFC2544 binary search and 9000B frames through bridge domain in 3-node topology
+
[https://jenkins.fd.io/view/csit/job/csit-vpp-perf-1606-all/12/robot/Tests/Suites/Performance/ Test Suites]
−
## tests/suites/performance/Long_Bridge_Domain_Intel-X520-DA2.robot:143:| Find PDR by using RFC2544 binary search and 9000B frames through bridge domain in 3-node topology
+
 
−
## tests/suites/performance/Long_Bridge_Domain_Intel-X520-DA2.robot:166:| Find NDR with 2 cores and rss 1 by using RFC2544 binary search and 64B frames through bridge domain in 3-node topology
+
===CSIT test suite list for VPP v16.09===
−
## tests/suites/performance/Long_Bridge_Domain_Intel-X520-DA2.robot:187:| Find PDR with 2 cores and rss 1 by using RFC2544 binary search and 64B frames through bridge domain in 3-node topology
+
 
−
## tests/suites/performance/Long_Bridge_Domain_Intel-X520-DA2.robot:211:| Find NDR with 2 cores and rss 1 by using RFC2544 binary search and 1518B frames through bridge domain in 3-node topology
+
[TO-DO]
−
## tests/suites/performance/Long_Bridge_Domain_Intel-X520-DA2.robot:232:| Find PDR with 2 cores and rss 1 by using RFC2544 binary search and 1518B frames through bridge domain in 3-node topology
+
−
## tests/suites/performance/Long_Bridge_Domain_Intel-X520-DA2.robot:256:| Find NDR with 2 cores and rss 1 by using RFC2544 binary search and 9000B frames through bridge domain in 3-node topology
+
−
## tests/suites/performance/Long_Bridge_Domain_Intel-X520-DA2.robot:276:| Find PDR with 2 cores and rss 1 by using RFC2544 binary search and 9000B frames through bridge domain in 3-node topology
+
−
## tests/suites/performance/Long_Bridge_Domain_Intel-X520-DA2.robot:299:| Find NDR with 4 cores and rss 2 by using RFC2544 binary search and 64B frames through bridge domain in 3-node topology
+
−
## tests/suites/performance/Long_Bridge_Domain_Intel-X520-DA2.robot:320:| Find PDR with 4 cores and rss 2 by using RFC2544 binary search and 64B frames through bridge domain in 3-node topology
+
−
## tests/suites/performance/Long_Bridge_Domain_Intel-X520-DA2.robot:33:| Find NDR by using RFC2544 binary search and 64B frames through bridge domain in 3-node topology
+
−
## tests/suites/performance/Long_Bridge_Domain_Intel-X520-DA2.robot:345:| Find NDR with 4 cores and rss 2 by using RFC2544 binary search and 1518B frames through bridge domain in 3-node topology
+
−
## tests/suites/performance/Long_Bridge_Domain_Intel-X520-DA2.robot:366:| Find PDR with 4 cores and rss 2 by using RFC2544 binary search and 1518B frames through bridge domain in 3-node topology
+
−
## tests/suites/performance/Long_Bridge_Domain_Intel-X520-DA2.robot:390:| Find NDR with 4 cores and rss 2 by using RFC2544 binary search and 9000B frames through bridge domain in 3-node topology
+
−
## tests/suites/performance/Long_Bridge_Domain_Intel-X520-DA2.robot:410:| Find PDR with 4 cores and rss 2 by using RFC2544 binary search and 9000B frames through bridge domain in 3-node topology
+
−
## tests/suites/performance/Long_Bridge_Domain_Intel-X520-DA2.robot:54:| Find PDR by using RFC2544 binary search and 64B frames through bridge domain in 3-node topology
+
−
## tests/suites/performance/Long_Bridge_Domain_Intel-X520-DA2.robot:78:| Find NDR by using RFC2544 binary search and 1518B frames through bridge domain in 3-node topology
+
−
## tests/suites/performance/Long_Bridge_Domain_Intel-X520-DA2.robot:99:| Find PDR by using RFC2544 binary search and 1518B frames through bridge domain in 3-node topology
+
−
## tests/suites/performance/Long_IPv4_Intel-X520-DA2.robot:103:| Find PDR by using RFC2544 binary search and 1518B frames through IPv4 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv4_Intel-X520-DA2.robot:127:| Find NDR by using RFC2544 binary search and 9000B frames through IPv4 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv4_Intel-X520-DA2.robot:147:| Find PDR by using RFC2544 binary search and 9000B frames through IPv4 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv4_Intel-X520-DA2.robot:170:| Find NDR with 2 cores and rss 1 by using RFC2544 binary search and 64B frames through IPv4 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv4_Intel-X520-DA2.robot:191:| Find PDR with 2 cores and rss 1 by using RFC2544 binary search and 64B frames through IPv4 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv4_Intel-X520-DA2.robot:215:| Find NDR with 2 cores and rss 1 by using RFC2544 binary search and 1518B frames through IPv4 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv4_Intel-X520-DA2.robot:236:| Find PDR with 2 cores and rss 1 by using RFC2544 binary search and 1518B frames through IPv4 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv4_Intel-X520-DA2.robot:260:| Find NDR with 2 cores and rss 1 by using RFC2544 binary search and 9000B frames through IPv4 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv4_Intel-X520-DA2.robot:280:| Find PDR with 2 cores and rss 1 by using RFC2544 binary search and 9000B frames through IPv4 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv4_Intel-X520-DA2.robot:303:| Find NDR with 4 cores and rss 2 by using RFC2544 binary search and 64B frames through IPv4 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv4_Intel-X520-DA2.robot:324:| Find PDR with 4 cores and rss 2 by using RFC2544 binary search and 64B frames through IPv4 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv4_Intel-X520-DA2.robot:348:| Find NDR with 4 cores and rss 2 by using RFC2544 binary search and 1518B frames through IPv4 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv4_Intel-X520-DA2.robot:369:| Find PDR with 4 cores and rss 2 by using RFC2544 binary search and 1518B frames through IPv4 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv4_Intel-X520-DA2.robot:37:| Find NDR by using RFC2544 binary search and 64B frames through IPv4 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv4_Intel-X520-DA2.robot:393:| Find NDR with 4 cores and rss 2 by using RFC2544 linear search and 9000B frames through IPv4 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv4_Intel-X520-DA2.robot:413:| Find PDR with 4 cores and rss 2 by using RFC2544 linear search and 9000B frames through IPv4 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv4_Intel-X520-DA2.robot:58:| Find PDR by using RFC2544 binary search and 64B frames through IPv4 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv4_Intel-X520-DA2.robot:82:| Find NDR by using RFC2544 binary search and 1518B frames through IPv4 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv6_Intel-X520-DA2.robot:122:| Find NDR by using RFC2544 binary search and 9000B frames through IPv6 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv6_Intel-X520-DA2.robot:142:| Find PDR by using RFC2544 binary search and 9000B frames through IPv6 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv6_Intel-X520-DA2.robot:165:| Find NDR with 2 cores and rss 1 by using RFC2544 binary search and 78B frames through IPv6 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv6_Intel-X520-DA2.robot:186:| Find PDR with 2 cores and rss 1 by using RFC2544 binary search and 78B frames through IPv6 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv6_Intel-X520-DA2.robot:210:| Find NDR with 2 cores and rss 1 by using RFC2544 binary search and 1518B frames through IPv6 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv6_Intel-X520-DA2.robot:231:| Find PDR with 2 cores and rss 1 by using RFC2544 binary search and 1518B frames through IPv6 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv6_Intel-X520-DA2.robot:255:| Find NDR with 2 cores and rss 1 by using RFC2544 binary search and 9000B frames through IPv6 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv6_Intel-X520-DA2.robot:275:| Find PDR with 2 cores and rss 1 by using RFC2544 binary search and 9000B frames through IPv6 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv6_Intel-X520-DA2.robot:298:| Find NDR with 4 cores and rss 2 by using RFC2544 binary search and 78B frames through IPv6 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv6_Intel-X520-DA2.robot:319:| Find PDR with 4 cores and rss 2 by using RFC2544 binary search and 78B frames through IPv6 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv6_Intel-X520-DA2.robot:32:| Find NDR by using RFC2544 binary search and 78B frames through IPv6 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv6_Intel-X520-DA2.robot:343:| Find NDR with 4 cores and rss 2 by using RFC2544 binary search and 1518B frames through IPv6 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv6_Intel-X520-DA2.robot:364:| Find PDR with 4 cores and rss 2 by using RFC2544 binary search and 1518B frames through IPv6 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv6_Intel-X520-DA2.robot:388:| Find NDR with 4 cores and rss 2 by using RFC2544 linear search and 9000B frames through IPv6 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv6_Intel-X520-DA2.robot:409:| Find PDR with 4 cores and rss 2 by using RFC2544 linear search and 9000B frames through IPv6 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv6_Intel-X520-DA2.robot:53:| Find PDR by using RFC2544 binary search and 78B frames through IPv6 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv6_Intel-X520-DA2.robot:77:| Find NDR by using RFC2544 binary search and 1518B frames through IPv6 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_IPv6_Intel-X520-DA2.robot:98:| Find PDR by using RFC2544 binary search and 1518B frames through IPv6 forwarding in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Dot1q_Intel-X520-DA2.robot:101:| Find NDR by using RFC2544 binary search and 1518B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Dot1q_Intel-X520-DA2.robot:131:| Find PDR by using RFC2544 binary search and 1518B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Dot1q_Intel-X520-DA2.robot:164:| Find NDR by using RFC2544 binary search and 9000B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Dot1q_Intel-X520-DA2.robot:193:| Find PDR by using RFC2544 binary search and 9000B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Dot1q_Intel-X520-DA2.robot:225:| Find NDR with 2 cores and rss 1 by using RFC2544 binary search and 64B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Dot1q_Intel-X520-DA2.robot:255:| Find PDR with 2 cores and rss 1 by using RFC2544 binary search and 64B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Dot1q_Intel-X520-DA2.robot:288:| Find NDR with 2 cores and rss 1 by using RFC2544 binary search and 1518B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Dot1q_Intel-X520-DA2.robot:319:| Find PDR with 2 cores and rss 1 by using RFC2544 binary search and 1518B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Dot1q_Intel-X520-DA2.robot:352:| Find NDR with 2 cores and rss 1 by using RFC2544 binary search and 9000B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Dot1q_Intel-X520-DA2.robot:382:| Find PDR with 2 cores and rss 1 by using RFC2544 binary search and 9000B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Dot1q_Intel-X520-DA2.robot:38:| Find NDR by using RFC2544 binary search and 64B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Dot1q_Intel-X520-DA2.robot:414:| Find NDR with 4 cores and rss 2 by using RFC2544 binary search and 64B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Dot1q_Intel-X520-DA2.robot:445:| Find PDR with 4 cores and rss 2 by using RFC2544 binary search and 64B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Dot1q_Intel-X520-DA2.robot:479:| Find NDR with 4 cores and rss 2 by using RFC2544 binary search and 1518B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Dot1q_Intel-X520-DA2.robot:510:| Find PDR with 4 cores and rss 2 by using RFC2544 binary search and 1518B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Dot1q_Intel-X520-DA2.robot:544:| Find NDR with 4 cores and rss 2 by using RFC2544 binary search and 9000B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Dot1q_Intel-X520-DA2.robot:574:| Find PDR with 4 cores and rss 2 by using RFC2544 binary search and 9000B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Dot1q_Intel-X520-DA2.robot:68:| Find PDR by using RFC2544 binary search and 64B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Intel-X520-DA2.robot:100:| Find PDR by using RFC2544 binary search and 1518B frames through L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Intel-X520-DA2.robot:124:| Find NDR by using RFC2544 binary search and 9000B frames through L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Intel-X520-DA2.robot:144:| Find PDR by using RFC2544 binary search and 9000B frames through L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Intel-X520-DA2.robot:167:| Find NDR with 2 cores and rss 1 by using RFC2544 binary search and 64B frames through L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Intel-X520-DA2.robot:188:| Find PDR with 2 cores and rss 1 by using RFC2544 binary search and 64B frames through L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Intel-X520-DA2.robot:212:| Find NDR with 2 cores and rss 1 by using RFC2544 binary search and 1518B frames through L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Intel-X520-DA2.robot:233:| Find PDR with 2 cores and rss 1 by using RFC2544 binary search and 1518B frames through L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Intel-X520-DA2.robot:257:| Find NDR with 2 cores and rss 1 by using RFC2544 binary search and 9000B frames through L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Intel-X520-DA2.robot:277:| Find PDR with 2 cores and rss 1 by using RFC2544 binary search and 9000B frames through L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Intel-X520-DA2.robot:300:| Find NDR with 4 cores and rss 2 by using RFC2544 binary search and 64B frames through L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Intel-X520-DA2.robot:321:| Find PDR with 4 cores and rss 2 by using RFC2544 binary search and 64B frames through L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Intel-X520-DA2.robot:345:| Find NDR with 4 cores and rss 2 by using RFC2544 binary search and 1518B frames through L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Intel-X520-DA2.robot:34:| Find NDR by using RFC2544 binary search and 64B frames through L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Intel-X520-DA2.robot:366:| Find PDR with 4 cores and rss 2 by using RFC2544 binary search and 1518B frames through L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Intel-X520-DA2.robot:390:| Find NDR with 4 cores and rss 2 by using RFC2544 binary search and 9000B frames through L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Intel-X520-DA2.robot:410:| Find PDR with 4 cores and rss 2 by using RFC2544 binary search and 9000B frames through L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Intel-X520-DA2.robot:55:| Find PDR by using RFC2544 binary search and 64B frames through L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Long_Xconnect_Intel-X520-DA2.robot:79:| Find NDR by using RFC2544 binary search and 1518B frames through L2 cross connect in 3-node topology
+
−
## tests/suites/performance/Short_Bridge_Domain_Intel-X520-DA2.robot:106:| 2core VPP with rss 1 passes 9000B frames through bridge domain at 2x 138,580pps in 3-node topology
+
−
## tests/suites/performance/Short_Bridge_Domain_Intel-X520-DA2.robot:121:| 4core VPP with rss 2 passes 64B frames through bridge domain at 2x 7.4Mpps in 3-node topology
+
−
## tests/suites/performance/Short_Bridge_Domain_Intel-X520-DA2.robot:137:| 4core VPP with rss 2 passes 1518B frames through bridge domain at 2x 812,743pps in 3-node topology
+
−
## tests/suites/performance/Short_Bridge_Domain_Intel-X520-DA2.robot:153:| 4core VPP with rss 2 passes 9000B frames through bridge domain at 2x 138,580pps in 3-node topology
+
−
## tests/suites/performance/Short_Bridge_Domain_Intel-X520-DA2.robot:27:| 1core VPP passes 64B frames through bridge domain at 2x 3.2Mpps in 3-node topology
+
−
## tests/suites/performance/Short_Bridge_Domain_Intel-X520-DA2.robot:43:| 1core VPP passes 1518B frames through bridge domain at 2x 812,743pps in 3-node topology
+
−
## tests/suites/performance/Short_Bridge_Domain_Intel-X520-DA2.robot:59:| 1core VPP passes 9000B frames through bridge domain at 2x 138,580pps in 3-node topology
+
−
## tests/suites/performance/Short_Bridge_Domain_Intel-X520-DA2.robot:74:| 2core VPP with rss 1 passes 64B frames through bridge domain at 2x 6.9Mpps in 3-node topology
+
−
## tests/suites/performance/Short_Bridge_Domain_Intel-X520-DA2.robot:90:| 2core VPP with rss 1 passes 1518B frames through bridge domain at 2x 812,743pps in 3-node topology
+
−
## tests/suites/performance/Short_IPv4_Intel-X520-DA2.robot:110:| 2core VPP with rss 1 passes 9000B frames through IPv4 forwarding at 2x 138,580pps in 3-node topology
+
−
## tests/suites/performance/Short_IPv4_Intel-X520-DA2.robot:125:| 4core VPP with rss 2 passes 64B frames through IPv4 forwarding at 2x 7.8Mpps in 3-node topology
+
−
## tests/suites/performance/Short_IPv4_Intel-X520-DA2.robot:141:| 4core VPP with rss 2 passes 1518B frames through IPv4 forwarding at 2x 812,743pps in 3-node topology
+
−
## tests/suites/performance/Short_IPv4_Intel-X520-DA2.robot:157:| 4core VPP with rss 2 passes 9000B frames through IPv4 forwarding at 2x 138,580pps in 3-node topology
+
−
## tests/suites/performance/Short_IPv4_Intel-X520-DA2.robot:31:| 1core VPP passes 64B frames through IPv4 forwarding at 2x 3.5Mpps in 3-node topology
+
−
## tests/suites/performance/Short_IPv4_Intel-X520-DA2.robot:47:| 1core VPP passes 1518B frames through IPv4 forwarding at 2x 812,743pps in 3-node topology
+
−
## tests/suites/performance/Short_IPv4_Intel-X520-DA2.robot:63:| 1core VPP passes 9000B frames through IPv4 forwarding at 2x 138,580pps in 3-node topology
+
−
## tests/suites/performance/Short_IPv4_Intel-X520-DA2.robot:78:| 2core VPP with rss 1 passes 64B frames through IPv4 forwarding at 2x 7.5Mpps in 3-node topology
+
−
## tests/suites/performance/Short_IPv4_Intel-X520-DA2.robot:94:| 2core VPP with rss 1 passes 1518B frames through IPv4 forwarding at 2x 812,743pps in 3-node topology
+
−
## tests/suites/performance/Short_IPv6_Intel-X520-DA2.robot:106:| 2core VPP with rss 1 passes 9000B frames through IPv6 forwarding at 2x 138,580pps in 3-node topology
+
−
## tests/suites/performance/Short_IPv6_Intel-X520-DA2.robot:121:| 4core VPP with rss 2 passes 78B frames through IPv6 forwarding at 2x 7.3Mpps in 3-node topology
+
−
## tests/suites/performance/Short_IPv6_Intel-X520-DA2.robot:137:| 4core VPP with rss 2 passes 1518B frames through IPv6 forwarding at 2x 812,743pps in 3-node topology
+
−
## tests/suites/performance/Short_IPv6_Intel-X520-DA2.robot:153:| 4core VPP with rss 2 passes 9000B frames through IPv6 forwarding at 2x 138,580pps in 3-node topology
+
−
## tests/suites/performance/Short_IPv6_Intel-X520-DA2.robot:27:| 1core VPP passes 78B frames through IPv6 forwarding at 2x 2.9Mpps in 3-node topology
+
−
## tests/suites/performance/Short_IPv6_Intel-X520-DA2.robot:43:| 1core VPP passes 1518B frames through IPv6 forwarding at 2x 812,743pps in 3-node topology
+
−
## tests/suites/performance/Short_IPv6_Intel-X520-DA2.robot:59:| 1core VPP passes 9000B frames through IPv6 forwarding at 2x 138,580pps in 3-node topology
+
−
## tests/suites/performance/Short_IPv6_Intel-X520-DA2.robot:74:| 2core VPP with rss 1 passes 78B frames through IPv6 forwarding at 2x 5.9Mpps in 3-node topology
+
−
## tests/suites/performance/Short_IPv6_Intel-X520-DA2.robot:90:| 2core VPP with rss 1 passes 1518B frames through IPv6 forwarding at 2x 812,743pps in 3-node topology
+
−
## tests/suites/performance/Short_Xconnect_Dot1q_Intel-X520-DA2.robot:108:| 2core VPP with rss 1 passes 64B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect at 2x5.8Mpps in 3-node topology
+
−
## tests/suites/performance/Short_Xconnect_Dot1q_Intel-X520-DA2.robot:134:| 2core VPP with rss 1 passes 1518B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect at 2x 720,000pps in 3-node topology
+
−
## tests/suites/performance/Short_Xconnect_Dot1q_Intel-X520-DA2.robot:160:| 2core VPP with rss 1 passes 9000B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect at 2x 120,000pps in 3-node topology
+
−
## tests/suites/performance/Short_Xconnect_Dot1q_Intel-X520-DA2.robot:185:| 4core VPP with rss 2 passes 64B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect at 2x9.0Mpps in 3-node topology
+
−
## tests/suites/performance/Short_Xconnect_Dot1q_Intel-X520-DA2.robot:211:| 4core VPP with rss 2 passes 1518B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect at 2x 720,000pps in 3-node topology
+
−
## tests/suites/performance/Short_Xconnect_Dot1q_Intel-X520-DA2.robot:237:| 4core VPP with rss 2 passes 9000B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect at 2x 120,000pps in 3-node topology
+
−
## tests/suites/performance/Short_Xconnect_Dot1q_Intel-X520-DA2.robot:31:| 1core VPP passes 64B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect at 2x2.9Mpps in 3-node topology
+
−
## tests/suites/performance/Short_Xconnect_Dot1q_Intel-X520-DA2.robot:57:| 1core VPP passes 1518B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect at 2x 720,000pps in 3-node topology
+
−
## tests/suites/performance/Short_Xconnect_Dot1q_Intel-X520-DA2.robot:83:| 1core VPP passes 9000B frames through VLAN dot1q sub-interfaces inter-connected using L2 cross connect at 2x 120,000pps in 3-node topology
+
−
## tests/suites/performance/Short_Xconnect_Intel-X520-DA2.robot:107:| 2core VPP with rss 1 passes 9000B frames through L2 cross connect at 2x 138,580pps in 3-node topology
+
−
## tests/suites/performance/Short_Xconnect_Intel-X520-DA2.robot:122:| 4core VPP with rss 2 passes 64B frames through L2 cross connect at 2x 9.3Mpps in 3-node topology
+
−
## tests/suites/performance/Short_Xconnect_Intel-X520-DA2.robot:138:| 4core VPP with rss 2 passes 1518B frames through L2 cross connect at 2x 812,743pps in 3-node topology
+
−
## tests/suites/performance/Short_Xconnect_Intel-X520-DA2.robot:154:| 4core VPP with rss 2 passes 9000B frames through L2 cross connect at 2x 138,580pps in 3-node topology
+
−
## tests/suites/performance/Short_Xconnect_Intel-X520-DA2.robot:28:| 1core VPP passes 64B frames through L2 cross connect at 2x 3.6Mpps in 3-node topology
+
−
## tests/suites/performance/Short_Xconnect_Intel-X520-DA2.robot:44:| 1core VPP passes 1518B frames through L2 cross connect at 2x 812,743pps in 3-node topology
+
−
## tests/suites/performance/Short_Xconnect_Intel-X520-DA2.robot:60:| 1core VPP passes 9000B frames through L2 cross connect at 2x 138,580pps in 3-node topology
+
−
## tests/suites/performance/Short_Xconnect_Intel-X520-DA2.robot:75:| 2core VPP with rss 1 passes 64B frames through L2 cross connect at 2x 8.3Mpps in 3-node topology
+
−
## tests/suites/performance/Short_Xconnect_Intel-X520-DA2.robot:91:| 2core VPP with rss 1 passes 1518B frames through L2 cross connect at 2x 812,743pps in 3-node topology
+
  
 
==Performance Test Cases - Plan and Status==
 
==Performance Test Cases - Plan and Status==
Line 185: Line 94:
 
Plan execution tracked on [https://jira.fd.io/secure/RapidBoard.jspa?rapidView=1&projectKey=CSIT CSIT jira]
 
Plan execution tracked on [https://jira.fd.io/secure/RapidBoard.jspa?rapidView=1&projectKey=CSIT CSIT jira]
  
−
Current list of identified csit-dev work items:
+
===CSIT-DEV plan for VPP v16.06===
  
 
# Long throughput benchmarks - libraries
 
# Long throughput benchmarks - libraries
Line 290: Line 199:
 
#* [TBD] unified performance trend dashboard
 
#* [TBD] unified performance trend dashboard
  
−
==csit-dev plan for VPP v16.09==
+
===CSIT-DEV plan for VPP v16.09===

Revision as of 07:08, 7 July 2016

CSIT Jenkins Jobs for Performance Tests

Jenkins Jobs
Task Job Triggers (patch comment VPP code CSIT code LF Testbed Status
Verify VPP code changes as they come - performance short tests vpp-csit-verify-hw-perf-master-short "verify-perf-short" VPP master branch + gerrit change under test csit-verified-tag TB1, TB2, TB3 WORKING
Verify VPP code changes as they come - performance long tests vpp-csit-verify-hw-perf-master-long "verify-perf-long" VPP master branch + gerrit change under test csit-verified-tag TB1, TB2, TB3 WORKING
Verify VPP code changes as they come - all performance tests vpp-csit-verify-hw-perf-master-all "verify-perf-all" VPP master branch + gerrit change under test csit-verified-tag TB1, TB2, TB3 WORKING
Verify CSIT code changes as they come - all performance tests csit-vpp-perf-master-all "verify-perf-all" vpp-master-verified vpp build csit master branch + gerrit change under test TB1, TB2, TB3 WORKING
Verify CSIT code changes as they come - performance long tests csit-vpp-perf-master-long "verify-perf-long" vpp-master-verified vpp build csit master branch + gerrit change under test TB1, TB2, TB3 WORKING
Verify CSIT code against VPP release 16.06 - all performance tests csit-vpp-perf-1606-all "verify-perf-all" vpp-master-verified vpp build csit stable/1606 branch TB1, TB2, TB3 WORKING
Verify CSIT code against VPP release 16.06 - performance long tests csit-vpp-perf-1606-long "verify-perf-long" vpp-master-verified vpp build csit stable/1606 branch TB1, TB2, TB3 WORKING

Performance Test Cases - Working

All 3 LF physical testbeds are all live - CSIT/CSIT LF testbed

CSIT test suite list for VPP v16.06

Test Suites

CSIT test suite list for VPP v16.09

[TO-DO]

Performance Test Cases - Plan and Status

For CSIT project to work and be useful, it is proposed that CSIT code and test cases development should be done in coordination with VPP Release Candidate content and release schedule. CSIT development work needs to be prioritized based on FD.io community needs and feedback, and csit-dev work distributed. To facilitate this, we compiled an initial list of proposed performance test cases that must, should, could be tested. Each csit-dev work item is prefixed with status and/or proposed priority relative to FD.io VPP release:

  • [Pn-Rm] – Proposed coverage of VPP functionality by FD.io CSIT functional and performance test cases.
    • Pn – CSIT development and integration priority; n=0,1,2, 0-for-MUST, 1-for-SHOULD, 2-for-COULD.
    • Rm – VPP major release, R1 stands for the first FD.io VPP release, R2 for the 2nd FD.io VPP release.
  • [DONE-Rm] - Done and working test cases, executed for VPP Rm code.
  • [TBD] - Development work scheduling priority to-be-defined.

Plan execution tracked on CSIT jira

CSIT-DEV plan for VPP v16.06

  1. Long throughput benchmarks - libraries
    1. [DONE-R1] IPv4 NonDropRate search
      • [DONE-R1] linear search [rfc2544] [gerrit-ref]
      • [DONE-R1] binary search [rfc2544] gerrit
      • [DONE-R1] BESTofN/WORSTofN search gerrit
      • [DONE-R1] combined binary+linear search gerrit
    2. [DONE-R1] L2 NonDropRate search [gerrit-ref]
    3. [DONE-R1] IPv6 NonDropRate search [gerrit-ref]
  2. Long throughput benchmarks - test cases
    1. [DONE-R1] IPv4 baseline NonDropRate search
      • [DONE-R1] linear search [rfc2544] [gerrit-ref]
      • [DONE-R1] binary search [rfc2544] [gerrit-ref]
      • [DONE-R1] BESTofN/WORSTofN search [gerrit-ref]
      • [DONE-R1] combined binary+linear search [gerrit-ref]
    2. [DONE-R1] L2 NonDropRate search
      • [DONE-R1] linear search [rfc2544] [gerrit-ref]
      • [DONE-R1] binary search [rfc2544] [gerrit-ref]
      • [DONE-R1] BESTofN/WORSTofN search [gerrit-ref]
      • [DONE-R1] combined binary+linear search [gerrit-ref]
    3. [DONE-R1] IPv6 NonDropRate search [gerrit-ref]
      • [DONE-R1] linear search [rfc2544] [gerrit-ref]
      • [DONE-R1] binary search [rfc2544] [gerrit-ref]
      • [DONE-R1] BESTofN/WORSTofN search [gerrit-ref]
      • [DONE-R1] combined binary+linear search [gerrit-ref]
  3. Short throughput benchmarks - libraries
    1. [DONE-R1] short IPv4 throughput test against reference NDR [gerrit-ref]
    2. [DONE-R1] short L2 throughput test against reference NDR [gerrit-ref]
    3. [DONE-R1] short IPv6 throughput test against reference NDR [gerrit-ref]
  4. Short throughput benchmarks - test cases
    1. [DONE-R1] short IPv4 throughput - routed-forwarding [gerrit-ref]
    2. [DONE-R1] short L2 throughput - bridge-domain, l2-xconnect [gerrit-ref]
    3. [DONE-R1] short IPv6 throughput - routed-forwarding [gerrit-ref]
  5. 3-node physical testbed - libraries
    • [DONE-R1] Create host topology files for tb2
    • [DONE-R1] Extend host topology with NIC type filtering
    • [DONE-R1] Create host topology files for tb1, tb3
  6. Multi-core multi-thread tests - libraries
    • [DONE-R1] multicore tests gerrit
  7. Large-scale FIB tests - libraries
    • [P1-R1] IPv4 same prefix length
    • [P2-R1] IPv4 varying prefix lengths
    • [P1-R1] IPv6 same prefix length
    • [P2-R1] IPv6 varying prefix lengths
    • [P1-R1] MAC addresses
  8. Packet encapsulations - test cases
    1. IP4 encapsulations
    2. [P1-R1] ip4-gre-ip4
    3. [P1-R2] ip4-ipsec-ip4
  9. IP6 encapsulations
    1. [P1-R1] ip4-o-ip6 softwire
      • [P1-R1] lightweight46 [rfc7596]
      • [P2-R1] map-e [rfc7597]
      • [P2-R1] map-t [rfc7599]
    2. [TBD] ip6-segment-routing
    3. [P1-R2] ip6-ipsec-ip6
  10. Security feature
    1. [DONE-R1] Classify IPv4 iACL
    2. [DONE-R1] Classify IPv6 iACL
    3. [DONE-R1] IPv4 COP
    4. [TBD] IPv6 COP
  11. L2 encapsulations
    1. [DONE-R1] l2-vlan-dot1q
    2. [DONE-R1] l2-vlan-dot1ad
    3. [P1-R1] l2-vxlan-ipv4
    4. [TBD] l2-eth-l2tpv3-ip4
    5. [TBD] l2-eth-l2tpv3-ip6
    6. [TBD] l2-eth-gre-ip4
    7. [TBD] l2-eth-gre-ip6
  12. VPP vNet topology baselines - libraries
    1. [TBD] Host stack baseline - Phy1-App-Phy2
      • [TBD] Reference host user-mode app, L3FWD-xconnect, DPDK driver per NIC type
    2. [TBD] Host stack VPP baseline - Phy1-VPP-Phy2
      • [TBD] Host VPP IPv4 baseline config, DPDK driver per NIC type
    3. [TBD] Guest stack baseline - Phy1-pcipt-AppVM-pcipt-Phy2
      • [TBD] Reference guest user-mode app, L3FWD-xconnect, DPDK driver per NIC type
    4. [TBD] Guest stack VPP baseline - Phy1-pcipt-VPPVM-pcipt-Phy2
      • [TBD] VPP IPv4 baseline config, DPDK driver per NIC type
    5. [TBD] Host and guest stack baseline - Phy1-VPP-AppVM-VPP-Phy2
      • [TBD] VPP IPv4 baseline config, vhost-user to AppVM
  13. vNet VPP topologies - libraries
    • [DONE-R1] Phy1-VPP-Phy2
    • [P0-R1] Phy1-VPP-VM-VPP-Phy2
  14. Traffic generator drivers
    1. [DONE-R1] T-Rex
      • [DONE-R1] T-Rex driver
      • [TBD] TRex support for packet delay and packet delay variation (T-REX support to be confirmed)
    2. [TBD] IXIA IxNetwork driver
      • [TBD] driver design
      • [TBD] driver implementation
        • [TBD] test case setup, teardown
        • [TBD] traffic stream configuration
        • [TBD] statistics retrieval
      • [TBD] latency measurements
        • [TBD] feasibility
        • [TBD] implementation
      • [TBD] integration with CSIT tests
    3. [TBD] Moongen driver
      • [TBD] verify requirements and available HW against latest MoonGen codebase
      • [TBD] CSIT integration
  15. Other work items

CSIT-DEV plan for VPP v16.09

Retrieved from "https://wiki.fd.io/index.php?title=CSIT/PerfTestPlan&oldid=2053"