Skip to end of metadata
Go to start of metadata
Attendees
Sl. No | Topic | Presenters | Notes |
---|
1 | Development Update |
| Work in Progress: - Qemu.
- Extracting NIC details from the deployed pod. It is straightforward for pci-id/nic-names, but get tricky with socketfiles. Socketfiles are different for memif and virtio_user.
- Tgen+Deployment and Node-Port configuration: automation.
- Results collection from vinperf-pod (on console results) - To decide whether the test is completed or not and collection results in PROX case.
|
2 | 2-weeks Off |
| No meeting for next 2 weeks. Next meeting 2nd March 2022. Will be available to run tests. |
3 | Kubernetes Dataplane Benchmarking - PROX and T-REX |
| - Prox:
- VPP – Unidirectional & Bidirectional – 5 topologies
- OVS – Unidirectional & Bidirectional – 5 topologies
- Trex:
- VPP – 3 topologies.
- net_memif and dummy isn’t supported.
- OVS –
- Current: virtio_user0
- Error: virtio_user not supported.
- TODO:
- Poor performances in some scenarios*
- Start writing the explanations- Whys
- Highlight issues with Traffic Generators* (Multi-core with prox)
- Run TRex with BSwLV
- Need to come-up with ‘golden-configuration’ – What is right configuration that will give best-performance (CNI technology – vswitches).
- separate core for each PMD
- More cores to VPP (topology 4 and 5) – Already the max (8 cores)… so, no use..
- To Check:
- More cores for trex (in Pod defn file, add resources) – Daniele to test.
- More cores for prox is not working***
- Increase queues (Not sure if it is possible). Memif (vpp) and vhostuser(ovs) – "Sridhar to check"
- Swap node – configuration? (Check with Luc).
|