Difference between revisions of "CSIT/PerfTestPlan"

From fd.io
Jump to: navigation, search
Line 1: Line 1:
 
__TOC__
 
__TOC__
−
==FD.io IT systems integration==
+
==CSIT Jenkins Jobs Testing Performance ==
  
−
Three Jenkins jobs for CSIT performance test cases are in place today:
+
# task: verify vpp code changes as they come - performance short tests
 +
#* job: [https://jenkins.fd.io/view/vpp/job/vpp-csit-verify-perf-short/ vpp-csit-verify-perf-short]
 +
#* triggers: "verify-perf-short" patch comment
 +
#* vpp code: vpp master branch PLUS gerrit change under test
 +
#* csit code: csit-verified-tag
 +
#* testbed: LF HW compute nodes - hw-tb1,tb2,tb3
 +
#* status: WORKING
 +
# task: verify vpp code changes as they come - performance long tests
 +
#* job: [https://jenkins.fd.io/view/vpp/job/vpp-csit-verify-perf-long/ vpp-csit-verify-perf-long]
 +
#* triggers: "verify-perf-long" patch comment
 +
#* vpp code: vpp master branch PLUS gerrit change under test
 +
#* csit code: csit-verified-tag
 +
#* testbed: LF HW compute nodes - hw-tb1,tb2,tb3
 +
#* status: WORKING
 +
# task: verify vpp code changes as they come - performance all tests
 +
#* job: [https://jenkins.fd.io/view/vpp/job/vpp-csit-verify-perf-all/ vpp-csit-verify-perf-all]
 +
#* triggers: "verify-perf-all" patch comment
 +
#* vpp code: vpp master branch PLUS gerrit change under test
 +
#* csit code: csit-verified-tag
 +
#* testbed: LF HW compute nodes - hw-tb1,tb2,tb3
 +
#* status: WORKING
 +
# task: verify csit code changes as they come - performance tests
 +
#* job: [https://jenkins.fd.io/view/csit/job/csit-vpp-perf-hw-all/ csit-vpp-perf-hw-all]
 +
#* triggers: gerrit change commit, "recheck" patch comment
 +
#* vpp code: vpp-master-verified vpp build
 +
#* csit code: csit master branch PLUS gerrit change
 +
#* testbed: LF HW compute nodes - hw-tb1,tb2,tb3
 +
#* status: WORKING
  
−
# Job name: '''csit-vpp-perf-hw'''
+
==Performance Test Cases - Working==
−
#* Description: This job is testing csit project against performance test cases
+
−
#** TODO items
+
−
#*** scope - currently only tb2, need to add other testbeds: tb1, tb3
+
−
#*** scope - tbX reservation script and tbX scheduler code already done and tested, needs to be used
+
−
#* Trigger: Comment "verify-perf-all" in proposed patch in CSIT project
+
−
#** TODO items
+
−
#*** consider adding later on "verify-perf-short", "verify-perf-long"
+
−
#* Status: WORKING
+
−
# Job name: '''vpp-verify-performance-long'''
+
−
#* Description: This job is testing vpp proposed patch against long performance test cases
+
−
#* Trigger: Comment "verify-perf-long" in proposed patch in VPP project
+
−
#** TODO items
+
−
#*** [IN REVIEW, pmikus] consider rename to "vpp-csit-verify-perf-long" [https://gerrit.fd.io/r/#/c/834/ gerrit]
+
−
#* Status: WORKING
+
−
# Job name: '''vpp-verify-performance-short'''
+
−
#* Description: This job is testing vpp proposed patch against short performance test cases
+
−
#* Trigger: Comment "verify-perf-short" in proposed patch in VPP project
+
−
#** TODO items
+
−
#*** [IN REVIEW, pmikus] consider rename to "vpp-csit-verify-perf-short" [https://gerrit.fd.io/r/#/c/834/ gerrit]
+
−
#* Status: WORKING
+
  
−
==CSIT performance test cases - working==
+
# All 3 LF physical testbeds are all live - hw-tb1,tb2,tb3.
−
 
+
# Performance test cases - 56 working in FD.io physical testbeds today.
−
# Performance test cases - 30 working in FD.io physical testbeds today.
+
−
#* hw-tb2 - physical testbed 2 is live.
+
−
#* hw-tb1, hw-tb2 - physical testbeds 1 and 2 are being onboarded.
+
−
# Last manual run results reports:
+
−
#* https://jenkins.fd.io/view/csit/job/csit-vpp-perf-hw-all/
+
−
#* https://jenkins.fd.io/view/vpp/job/vpp-verify-performance-long/
+
−
#* https://jenkins.fd.io/view/vpp/job/vpp-verify-performance-short/
+
 
# List of working performance test cases
 
# List of working performance test cases
−
#* ~/csit$ grep "^| [a-zA-Z1-9]" -nr tests | grep -vi " | "  | sort | grep performance
+
## ~/csit$ grep "^| [a-zA-Z1-9]" -nr tests | grep -vi " | "  | sort | grep performance
−
## tests/suites/performance/long_bridge_domain.robot:103:| Find NDR with 4 cores and rss 2 by using RFC2544 linear search and 64B frames through bridge domain in 3-node topology
+
## tests/suites/performance/long_bridge_domain.robot:114:| Find NDR with 2 cores and rss 1 by using RFC2544 linear search and 9000B frames through bridge domain in 3-node topology
−
## tests/suites/performance/long_bridge_domain.robot:25:| Find NDR by using RFC2544 linear search and 64B frames through bridge domain in 3-node topology
+
## tests/suites/performance/long_bridge_domain.robot:131:| Find NDR with 4 cores and rss 2 by using RFC2544 linear search and 64B frames through bridge domain in 3-node topology
−
## tests/suites/performance/long_bridge_domain.robot:44:| Find NDR by using RFC2544 linear search and 1518B frames through bridge domain in 3-node topology
+
## tests/suites/performance/long_bridge_domain.robot:148:| Find NDR with 4 cores and rss 2 by using RFC2544 linear search and 1518B frames through bridge domain in 3-node topology
 +
## tests/suites/performance/long_bridge_domain.robot:165:| Find NDR with 4 cores and rss 2 by using RFC2544 linear search and 9000B frames through bridge domain in 3-node topology
 +
## tests/suites/performance/long_bridge_domain.robot:31:| Find NDR by using RFC2544 linear search and 64B frames through bridge domain in 3-node topology
 +
## tests/suites/performance/long_bridge_domain.robot:47:| Find NDR by using RFC2544 linear search and 1518B frames through bridge domain in 3-node topology
 
## tests/suites/performance/long_bridge_domain.robot:64:| Find NDR by using RFC2544 linear search and 9000B frames through bridge domain in 3-node topology
 
## tests/suites/performance/long_bridge_domain.robot:64:| Find NDR by using RFC2544 linear search and 9000B frames through bridge domain in 3-node topology
−
## tests/suites/performance/long_bridge_domain.robot:84:| Find NDR with 2 cores and rss 1 by using RFC2544 linear search and 64B frames through bridge domain in 3-node topology
+
## tests/suites/performance/long_bridge_domain.robot:81:| Find NDR with 2 cores and rss 1 by using RFC2544 linear search and 64B frames through bridge domain in 3-node topology
−
## tests/suites/performance/long_ipv4.robot:107:| Find NDR with 4 cores and rss 2 by using RFC2544 linear search and 64B frames through IPv4 forwarding in 3-node topology
+
## tests/suites/performance/long_bridge_domain.robot:97:| Find NDR with 2 cores and rss 1 by using RFC2544 linear search and 1518B frames through bridge domain in 3-node topology
−
## tests/suites/performance/long_ipv4.robot:29:| Find NDR by using RFC2544 linear search and 64B frames through IPv4 forwarding in 3-node topology
+
## tests/suites/performance/long_ipv4.robot:101:| Find NDR with 2 cores and rss 1 by using RFC2544 linear search and 1518B frames through IPv4 forwarding in 3-node topology
−
## tests/suites/performance/long_ipv4.robot:48:| Find NDR by using RFC2544 linear search and 1518B frames through IPv4 forwarding in 3-node topology
+
## tests/suites/performance/long_ipv4.robot:118:| Find NDR with 2 cores and rss 1 by using RFC2544 linear search and 9000B frames through IPv4 forwarding in 3-node topology
 +
## tests/suites/performance/long_ipv4.robot:135:| Find NDR with 4 cores and rss 2 by using RFC2544 linear search and 64B frames through IPv4 forwarding in 3-node topology
 +
## tests/suites/performance/long_ipv4.robot:152:| Find NDR with 4 cores and rss 2 by using RFC2544 linear search and 1518B frames through IPv4 forwarding in 3-node topology
 +
## tests/suites/performance/long_ipv4.robot:169:| 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.robot:186:| Find NDR with 2 cores by using RFC2544 binary search and 64B frames through IPv4 forwarding in 3-node topology
 +
## tests/suites/performance/long_ipv4.robot:204:| 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.robot:35:| Find NDR by using RFC2544 linear search and 64B frames through IPv4 forwarding in 3-node topology
 +
## tests/suites/performance/long_ipv4.robot:51:| Find NDR by using RFC2544 linear search and 1518B frames through IPv4 forwarding in 3-node topology
 
## tests/suites/performance/long_ipv4.robot:68:| Find NDR by using RFC2544 linear search and 9000B frames through IPv4 forwarding in 3-node topology
 
## tests/suites/performance/long_ipv4.robot:68:| Find NDR by using RFC2544 linear search and 9000B frames through IPv4 forwarding in 3-node topology
−
## tests/suites/performance/long_ipv4.robot:88:| Find NDR with 2 cores and rss 1 by using RFC2544 linear search and 64B frames through IPv4 forwarding in 3-node topology
+
## tests/suites/performance/long_ipv4.robot:85:| Find NDR with 2 cores and rss 1 by using RFC2544 linear search and 64B frames through IPv4 forwarding in 3-node topology
−
## tests/suites/performance/long_xconnect.robot:107:| Find NDR with 4 cores and rss 2 by using RFC2544 linear search and 64B frames through L2 cross connect in 3-node topology
+
## tests/suites/performance/long_xconnect.robot:113:| Find NDR with 2 cores and rss 1 by using RFC2544 linear search and 9000B frames through L2 cross connect in 3-node topology
 +
## tests/suites/performance/long_xconnect.robot:130:| Find NDR with 4 cores and rss 2 by using RFC2544 linear search and 64B frames through L2 cross connect in 3-node topology
 +
## tests/suites/performance/long_xconnect.robot:147:| Find NDR with 4 cores and rss 2 by using RFC2544 linear search and 1518B frames through L2 cross connect in 3-node topology
 +
## tests/suites/performance/long_xconnect.robot:164:| Find NDR with 4 cores and rss 2 by using RFC2544 linear search and 9000B frames through L2 cross connect in 3-node topology
 
## tests/suites/performance/long_xconnect.robot:32:| Find NDR by using RFC2544 linear search and 64B frames through L2 cross connect in 3-node topology
 
## tests/suites/performance/long_xconnect.robot:32:| Find NDR by using RFC2544 linear search and 64B frames through L2 cross connect in 3-node topology
−
## tests/suites/performance/long_xconnect.robot:50:| Find NDR by using RFC2544 linear search and 1518B frames through L2 cross connect in 3-node topology
+
## tests/suites/performance/long_xconnect.robot:48:| Find NDR by using RFC2544 linear search and 1518B frames through L2 cross connect in 3-node topology
−
## tests/suites/performance/long_xconnect.robot:69:| Find NDR by using RFC2544 linear search and 9000B frames through L2 cross connect in 3-node topology
+
## tests/suites/performance/long_xconnect.robot:64:| Find NDR by using RFC2544 linear search and 9000B frames through L2 cross connect in 3-node topology
−
## tests/suites/performance/long_xconnect.robot:88:| Find NDR with 2 cores and rss 1 by using RFC2544 linear search and 64B frames through L2 cross connect in 3-node topology
+
## tests/suites/performance/long_xconnect.robot:80:| Find NDR with 2 cores and rss 1 by using RFC2544 linear search and 64B frames through L2 cross connect in 3-node topology
−
## tests/suites/performance/short_bridge_domain.robot:25:| 1core VPP passes 64B frames through bridge domain at 2x 3.5Mpps in 3-node topology
+
## tests/suites/performance/long_xconnect.robot:96:| Find NDR with 2 cores and rss 1 by using RFC2544 linear search and 1518B frames through L2 cross connect in 3-node topology
−
## tests/suites/performance/short_bridge_domain.robot:41:| 1core VPP passes 1518B frames through bridge domain at 2x 10Gbps in 3-node topology
+
## tests/suites/performance/short_bridge_domain.robot:103:| 4core VPP with rss 2 passes 64B frames through bridge domain at 2x 7.9Mpps in 3-node topology
−
## tests/suites/performance/short_bridge_domain.robot:57:| 1core VPP passes 9000B frames through bridge domain at 2x 10Gbps in 3-node topology
+
## tests/suites/performance/short_bridge_domain.robot:116:| 4core VPP with rss 2 passes 1518B frames through bridge domain at 2x 10Gbps in 3-node topology
−
## tests/suites/performance/short_bridge_domain.robot:73:| 2core VPP with rss 1 passes 64B frames through bridge domain at 2x 7.6Mpps in 3-node topology
+
## tests/suites/performance/short_bridge_domain.robot:129:| 4core VPP with rss 2 passes 9000B frames through bridge domain at 2x 10Gbps in 3-node topology
−
## tests/suites/performance/short_bridge_domain.robot:89:| 4core VPP with rss 2 passes 64B frames through bridge domain at 2x 8.6Mpps in 3-node topology
+
## tests/suites/performance/short_bridge_domain.robot:25:| 1core VPP passes 64B frames through bridge domain at 2x 3.2Mpps in 3-node topology
−
## tests/suites/performance/short_ipv4.robot:29:| 1core VPP passes 64B frames through IPv4 forwarding at 2x 3.5mpps in 3-node topology
+
## tests/suites/performance/short_bridge_domain.robot:38:| 1core VPP passes 1518B frames through bridge domain at 2x 10Gbps in 3-node topology
−
## tests/suites/performance/short_ipv4.robot:45:| 1core VPP passes 1518B frames through IPv4 forwarding at 2x 10gbps in 3-node topology
+
## tests/suites/performance/short_bridge_domain.robot:51:| 1core VPP passes 9000B frames through bridge domain at 2x 10Gbps in 3-node topology
−
## tests/suites/performance/short_ipv4.robot:61:| 1core VPP passes 9000B frames through IPv4 forwarding at 2x 10gbps in 3-node topology
+
## tests/suites/performance/short_bridge_domain.robot:64:| 2core VPP with rss 1 passes 64B frames through bridge domain at 2x 6.9Mpps in 3-node topology
−
## tests/suites/performance/short_ipv4.robot:77:| 2core VPP with rss 1 passes 64B frames through IPv4 forwarding at 2x 8.2mpps in 3-node topology
+
## tests/suites/performance/short_bridge_domain.robot:77:| 2core VPP with rss 1 passes 1518B frames through bridge domain at 2x 10Gbps in 3-node topology
−
## tests/suites/performance/short_ipv4.robot:93:| 4core VPP with rss 2 passes 64B frames through IPv4 forwarding at 2x 9.2mpps in 3-node topology
+
## tests/suites/performance/short_bridge_domain.robot:90:| 2core VPP with rss 1 passes 9000B frames through bridge domain at 2x 10Gbps in 3-node topology
−
## tests/suites/performance/short_xconnect.robot:26:| 1core VPP passes 64B frames through L2 cross connect at 2x 3.5mpps in 3-node topology
+
## tests/suites/performance/short_ipv4.robot:107:| 4core VPP with rss 2 passes 64B frames through IPv4 forwarding at 2x 7.8Mpps in 3-node topology
−
## tests/suites/performance/short_xconnect.robot:42:| 1core VPP passes 1518B frames through L2 cross connect at 2x 10gbps in 3-node topology
+
## tests/suites/performance/short_ipv4.robot:120:| 4core VPP with rss 2 passes 1518B frames through IPv4 forwarding at 2x 10Gbps in 3-node topology
−
## tests/suites/performance/short_xconnect.robot:58:| 1core VPP passes 9000B frames through L2 cross connect at 2x 10gbps in 3-node topology
+
## tests/suites/performance/short_ipv4.robot:133:| 4core VPP with rss 2 passes 9000B frames through IPv4 forwarding at 2x 10Gbps in 3-node topology
−
## tests/suites/performance/short_xconnect.robot:74:| 2core VPP with rss 1 passes 64B frames through L2 cross connect at 2x 11.0mpps in 3-node topology
+
## tests/suites/performance/short_ipv4.robot:29:| 1core VPP passes 64B frames through IPv4 forwarding at 2x 3.5Mpps in 3-node topology
−
## tests/suites/performance/short_xconnect.robot:90:| 4core VPP with rss 2 passes 64B frames through L2 cross connect at 2x 11.6mpps in 3-node topology
+
## tests/suites/performance/short_ipv4.robot:42:| 1core VPP passes 1518B frames through IPv4 forwarding at 2x 10Gbps in 3-node topology
 +
## tests/suites/performance/short_ipv4.robot:55:| 1core VPP passes 9000B frames through IPv4 forwarding at 2x 10Gbps in 3-node topology
 +
## tests/suites/performance/short_ipv4.robot:68:| 2core VPP with rss 1 passes 64B frames through IPv4 forwarding at 2x 7.5Mpps in 3-node topology
 +
## tests/suites/performance/short_ipv4.robot:81:| 2core VPP with rss 1 passes 1518B frames through IPv4 forwarding at 2x 10Gbps in 3-node topology
 +
## tests/suites/performance/short_ipv4.robot:94:| 2core VPP with rss 1 passes 9000B frames through IPv4 forwarding at 2x 10Gbps in 3-node topology
 +
## tests/suites/performance/short_xconnect_Intel-X520-DA2.robot:106:| 4core VPP with rss 2 passes 64B frames through L2 cross connect at 2x 9.9Mpps in 3-node topology
 +
## tests/suites/performance/short_xconnect_Intel-X520-DA2.robot:119:| 4core VPP with rss 2 passes 1518B frames through L2 cross connect at 2x 10Gbps in 3-node topology
 +
## tests/suites/performance/short_xconnect_Intel-X520-DA2.robot:132:| 4core VPP with rss 2 passes 9000B frames through L2 cross connect at 2x 10Gbps 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.8Mpps in 3-node topology
 +
## tests/suites/performance/short_xconnect_Intel-X520-DA2.robot:41:| 1core VPP passes 1518B frames through L2 cross connect at 2x 10Gbps in 3-node topology
 +
## tests/suites/performance/short_xconnect_Intel-X520-DA2.robot:54:| 1core VPP passes 9000B frames through L2 cross connect at 2x 10Gbps in 3-node topology
 +
## tests/suites/performance/short_xconnect_Intel-X520-DA2.robot:67:| 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:80:| 2core VPP with rss 1 passes 1518B frames through L2 cross connect at 2x 10Gbps in 3-node topology
 +
## tests/suites/performance/short_xconnect_Intel-X520-DA2.robot:93:| 2core VPP with rss 1 passes 9000B frames through L2 cross connect at 2x 10Gbps in 3-node topology
  
−
==CSIT performance test cases - plan and status==
+
==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.
 
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.
Line 77: Line 103:
 
* [DONE-Rm] - Done and working test cases, executed for VPP Rm code.
 
* [DONE-Rm] - Done and working test cases, executed for VPP Rm code.
 
* [TBD] - Development work scheduling priority to-be-defined.
 
* [TBD] - Development work scheduling priority to-be-defined.
 +
 +
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:
 
Current list of identified csit-dev work items:

Revision as of 13:15, 27 April 2016

CSIT Jenkins Jobs Testing Performance

  1. task: verify vpp code changes as they come - performance short tests
    • job: vpp-csit-verify-perf-short
    • triggers: "verify-perf-short" patch comment
    • vpp code: vpp master branch PLUS gerrit change under test
    • csit code: csit-verified-tag
    • testbed: LF HW compute nodes - hw-tb1,tb2,tb3
    • status: WORKING
  2. task: verify vpp code changes as they come - performance long tests
    • job: vpp-csit-verify-perf-long
    • triggers: "verify-perf-long" patch comment
    • vpp code: vpp master branch PLUS gerrit change under test
    • csit code: csit-verified-tag
    • testbed: LF HW compute nodes - hw-tb1,tb2,tb3
    • status: WORKING
  3. task: verify vpp code changes as they come - performance all tests
    • job: vpp-csit-verify-perf-all
    • triggers: "verify-perf-all" patch comment
    • vpp code: vpp master branch PLUS gerrit change under test
    • csit code: csit-verified-tag
    • testbed: LF HW compute nodes - hw-tb1,tb2,tb3
    • status: WORKING
  4. task: verify csit code changes as they come - performance tests
    • job: csit-vpp-perf-hw-all
    • triggers: gerrit change commit, "recheck" patch comment
    • vpp code: vpp-master-verified vpp build
    • csit code: csit master branch PLUS gerrit change
    • testbed: LF HW compute nodes - hw-tb1,tb2,tb3
    • status: WORKING

Performance Test Cases - Working

  1. All 3 LF physical testbeds are all live - hw-tb1,tb2,tb3.
  2. Performance test cases - 56 working in FD.io physical testbeds today.
  3. List of working performance test cases
    1. ~/csit$ grep "^| [a-zA-Z1-9]" -nr tests | grep -vi " | " | sort | grep performance
    2. tests/suites/performance/long_bridge_domain.robot:114:| Find NDR with 2 cores and rss 1 by using RFC2544 linear search and 9000B frames through bridge domain in 3-node topology
    3. tests/suites/performance/long_bridge_domain.robot:131:| Find NDR with 4 cores and rss 2 by using RFC2544 linear search and 64B frames through bridge domain in 3-node topology
    4. tests/suites/performance/long_bridge_domain.robot:148:| Find NDR with 4 cores and rss 2 by using RFC2544 linear search and 1518B frames through bridge domain in 3-node topology
    5. tests/suites/performance/long_bridge_domain.robot:165:| Find NDR with 4 cores and rss 2 by using RFC2544 linear search and 9000B frames through bridge domain in 3-node topology
    6. tests/suites/performance/long_bridge_domain.robot:31:| Find NDR by using RFC2544 linear search and 64B frames through bridge domain in 3-node topology
    7. tests/suites/performance/long_bridge_domain.robot:47:| Find NDR by using RFC2544 linear search and 1518B frames through bridge domain in 3-node topology
    8. tests/suites/performance/long_bridge_domain.robot:64:| Find NDR by using RFC2544 linear search and 9000B frames through bridge domain in 3-node topology
    9. tests/suites/performance/long_bridge_domain.robot:81:| Find NDR with 2 cores and rss 1 by using RFC2544 linear search and 64B frames through bridge domain in 3-node topology
    10. tests/suites/performance/long_bridge_domain.robot:97:| Find NDR with 2 cores and rss 1 by using RFC2544 linear search and 1518B frames through bridge domain in 3-node topology
    11. tests/suites/performance/long_ipv4.robot:101:| Find NDR with 2 cores and rss 1 by using RFC2544 linear search and 1518B frames through IPv4 forwarding in 3-node topology
    12. tests/suites/performance/long_ipv4.robot:118:| Find NDR with 2 cores and rss 1 by using RFC2544 linear search and 9000B frames through IPv4 forwarding in 3-node topology
    13. tests/suites/performance/long_ipv4.robot:135:| Find NDR with 4 cores and rss 2 by using RFC2544 linear search and 64B frames through IPv4 forwarding in 3-node topology
    14. tests/suites/performance/long_ipv4.robot:152:| Find NDR with 4 cores and rss 2 by using RFC2544 linear search and 1518B frames through IPv4 forwarding in 3-node topology
    15. tests/suites/performance/long_ipv4.robot:169:| Find NDR with 4 cores and rss 2 by using RFC2544 linear search and 9000B frames through IPv4 forwarding in 3-node topology
    16. tests/suites/performance/long_ipv4.robot:186:| Find NDR with 2 cores by using RFC2544 binary search and 64B frames through IPv4 forwarding in 3-node topology
    17. tests/suites/performance/long_ipv4.robot:204:| Find NDR with 4 cores and rss 2 by using RFC2544 binary search and 64B frames through IPv4 forwarding in 3-node topology
    18. tests/suites/performance/long_ipv4.robot:35:| Find NDR by using RFC2544 linear search and 64B frames through IPv4 forwarding in 3-node topology
    19. tests/suites/performance/long_ipv4.robot:51:| Find NDR by using RFC2544 linear search and 1518B frames through IPv4 forwarding in 3-node topology
    20. tests/suites/performance/long_ipv4.robot:68:| Find NDR by using RFC2544 linear search and 9000B frames through IPv4 forwarding in 3-node topology
    21. tests/suites/performance/long_ipv4.robot:85:| Find NDR with 2 cores and rss 1 by using RFC2544 linear search and 64B frames through IPv4 forwarding in 3-node topology
    22. tests/suites/performance/long_xconnect.robot:113:| Find NDR with 2 cores and rss 1 by using RFC2544 linear search and 9000B frames through L2 cross connect in 3-node topology
    23. tests/suites/performance/long_xconnect.robot:130:| Find NDR with 4 cores and rss 2 by using RFC2544 linear search and 64B frames through L2 cross connect in 3-node topology
    24. tests/suites/performance/long_xconnect.robot:147:| Find NDR with 4 cores and rss 2 by using RFC2544 linear search and 1518B frames through L2 cross connect in 3-node topology
    25. tests/suites/performance/long_xconnect.robot:164:| Find NDR with 4 cores and rss 2 by using RFC2544 linear search and 9000B frames through L2 cross connect in 3-node topology
    26. tests/suites/performance/long_xconnect.robot:32:| Find NDR by using RFC2544 linear search and 64B frames through L2 cross connect in 3-node topology
    27. tests/suites/performance/long_xconnect.robot:48:| Find NDR by using RFC2544 linear search and 1518B frames through L2 cross connect in 3-node topology
    28. tests/suites/performance/long_xconnect.robot:64:| Find NDR by using RFC2544 linear search and 9000B frames through L2 cross connect in 3-node topology
    29. tests/suites/performance/long_xconnect.robot:80:| Find NDR with 2 cores and rss 1 by using RFC2544 linear search and 64B frames through L2 cross connect in 3-node topology
    30. tests/suites/performance/long_xconnect.robot:96:| Find NDR with 2 cores and rss 1 by using RFC2544 linear search and 1518B frames through L2 cross connect in 3-node topology
    31. tests/suites/performance/short_bridge_domain.robot:103:| 4core VPP with rss 2 passes 64B frames through bridge domain at 2x 7.9Mpps in 3-node topology
    32. tests/suites/performance/short_bridge_domain.robot:116:| 4core VPP with rss 2 passes 1518B frames through bridge domain at 2x 10Gbps in 3-node topology
    33. tests/suites/performance/short_bridge_domain.robot:129:| 4core VPP with rss 2 passes 9000B frames through bridge domain at 2x 10Gbps in 3-node topology
    34. tests/suites/performance/short_bridge_domain.robot:25:| 1core VPP passes 64B frames through bridge domain at 2x 3.2Mpps in 3-node topology
    35. tests/suites/performance/short_bridge_domain.robot:38:| 1core VPP passes 1518B frames through bridge domain at 2x 10Gbps in 3-node topology
    36. tests/suites/performance/short_bridge_domain.robot:51:| 1core VPP passes 9000B frames through bridge domain at 2x 10Gbps in 3-node topology
    37. tests/suites/performance/short_bridge_domain.robot:64:| 2core VPP with rss 1 passes 64B frames through bridge domain at 2x 6.9Mpps in 3-node topology
    38. tests/suites/performance/short_bridge_domain.robot:77:| 2core VPP with rss 1 passes 1518B frames through bridge domain at 2x 10Gbps in 3-node topology
    39. tests/suites/performance/short_bridge_domain.robot:90:| 2core VPP with rss 1 passes 9000B frames through bridge domain at 2x 10Gbps in 3-node topology
    40. tests/suites/performance/short_ipv4.robot:107:| 4core VPP with rss 2 passes 64B frames through IPv4 forwarding at 2x 7.8Mpps in 3-node topology
    41. tests/suites/performance/short_ipv4.robot:120:| 4core VPP with rss 2 passes 1518B frames through IPv4 forwarding at 2x 10Gbps in 3-node topology
    42. tests/suites/performance/short_ipv4.robot:133:| 4core VPP with rss 2 passes 9000B frames through IPv4 forwarding at 2x 10Gbps in 3-node topology
    43. tests/suites/performance/short_ipv4.robot:29:| 1core VPP passes 64B frames through IPv4 forwarding at 2x 3.5Mpps in 3-node topology
    44. tests/suites/performance/short_ipv4.robot:42:| 1core VPP passes 1518B frames through IPv4 forwarding at 2x 10Gbps in 3-node topology
    45. tests/suites/performance/short_ipv4.robot:55:| 1core VPP passes 9000B frames through IPv4 forwarding at 2x 10Gbps in 3-node topology
    46. tests/suites/performance/short_ipv4.robot:68:| 2core VPP with rss 1 passes 64B frames through IPv4 forwarding at 2x 7.5Mpps in 3-node topology
    47. tests/suites/performance/short_ipv4.robot:81:| 2core VPP with rss 1 passes 1518B frames through IPv4 forwarding at 2x 10Gbps in 3-node topology
    48. tests/suites/performance/short_ipv4.robot:94:| 2core VPP with rss 1 passes 9000B frames through IPv4 forwarding at 2x 10Gbps in 3-node topology
    49. tests/suites/performance/short_xconnect_Intel-X520-DA2.robot:106:| 4core VPP with rss 2 passes 64B frames through L2 cross connect at 2x 9.9Mpps in 3-node topology
    50. tests/suites/performance/short_xconnect_Intel-X520-DA2.robot:119:| 4core VPP with rss 2 passes 1518B frames through L2 cross connect at 2x 10Gbps in 3-node topology
    51. tests/suites/performance/short_xconnect_Intel-X520-DA2.robot:132:| 4core VPP with rss 2 passes 9000B frames through L2 cross connect at 2x 10Gbps in 3-node topology
    52. tests/suites/performance/short_xconnect_Intel-X520-DA2.robot:28:| 1core VPP passes 64B frames through L2 cross connect at 2x 3.8Mpps in 3-node topology
    53. tests/suites/performance/short_xconnect_Intel-X520-DA2.robot:41:| 1core VPP passes 1518B frames through L2 cross connect at 2x 10Gbps in 3-node topology
    54. tests/suites/performance/short_xconnect_Intel-X520-DA2.robot:54:| 1core VPP passes 9000B frames through L2 cross connect at 2x 10Gbps in 3-node topology
    55. tests/suites/performance/short_xconnect_Intel-X520-DA2.robot:67:| 2core VPP with rss 1 passes 64B frames through L2 cross connect at 2x 8.3Mpps in 3-node topology
    56. tests/suites/performance/short_xconnect_Intel-X520-DA2.robot:80:| 2core VPP with rss 1 passes 1518B frames through L2 cross connect at 2x 10Gbps in 3-node topology
    57. tests/suites/performance/short_xconnect_Intel-X520-DA2.robot:93:| 2core VPP with rss 1 passes 9000B frames through L2 cross connect at 2x 10Gbps in 3-node topology

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

Current list of identified csit-dev work items:

  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. [P0-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. [P0-R1] IPv6 NonDropRate search [gerrit-ref]
      • [P0-R1] linear search [rfc2544] [gerrit-ref]
      • [P0-R1] binary search [rfc2544] [gerrit-ref]
      • [P0-R1] BESTofN/WORSTofN search [gerrit-ref]
      • [P0-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. [P0-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. [P0-R1] short IPv6 throughput - routed-forwarding [gerrit-ref]
  5. 3-node physical testbed - libraries
    • [DONE-R1] Create host topology files for tb2
    • [P0-R1] Extend host topology with NIC type filtering
    • [P0-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. L2 encapsulations
    1. [P0-R1] l2-vlan-dot1q
    2. [P2-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
  11. 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
  12. vNet VPP topologies - libraries
    • [DONE-R1] Phy1-VPP-Phy2
    • [P0-R1] Phy1-VPP-VM-VPP-Phy2
  13. 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
  14. Other work items
Retrieved from "https://wiki.fd.io/index.php?title=CSIT/PerfTestPlan&oldid=990"