January 4, 2020

308 words 2 mins read

Improve the performance of GTP-U and Kube-Proxy Using VPP

Improve the performance of GTP-U and Kube-Proxy Using VPP

Come to this combined session where you will hear about:Improve the Performance of Kubernetes Cluster with VPP Based Router and Load BalancerIn current kubernetes environment, the container networks …

Talk Title Improve the performance of GTP-U and Kube-Proxy Using VPP
Speakers Hongjun Ni (Senior Software Engineer, Intel)
Conference Open Source Summit North America
Conf Tag
Location Los Angeles, CA, United States
Date Sep 10-14, 2017
URL Talk Page
Slides Talk Slides
Video

Come to this combined session where you will hear about:Improve the Performance of Kubernetes Cluster with VPP Based Router and Load BalancerIn current kubernetes environment, the container network’s data paths are all in kernel space:Container connects to the host with Linux virtual Ethernet device (VETH), kernel routing rulesAnd iptables rules enables the connection of the container from/to other containers or external Hosts; the default (which gains best performance) load balancer for the kube-proxy are also Implemented with iptables. This presentation will give another approach to enable the container Network with an userspace application named VPP to archive much better performance, two key technologies are used:1> Virtio_user based data path to archive best performance for virtual NICs.2> VPP load balancer to enable load balancer in userspace to archive better performance for kube-proxySix Ways to Improve Data Plane Performance in VPP and ContainerVPP is a high performance, packet-processing stack that can run on commodity CPUs. But for some developers, if they did not know some tricks, they could not develop high performance data plane using VPP. The presentation will show six ways to optimize the data plane performance in VPP and container.It includes below key elements:1) One-loop, Dual-loop and Quad-loop and performance evaluation.2) Packet prefetching and performance evaluation.3) Bypass first routing lookup and performance evaluation.4) Bypass second routing lookup and performance evaluation.5) Handle packet header in advance and performance evaluation.6) Tweak startup configuration in container and performance evaluation.

comments powered by Disqus