Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

Tối ưu hiệu năng đáp ứng các yêu cầu của hệ thống 4G core

136 vues

Publié le

Tối ưu hiệu năng đáp ứng các yêu cầu của hệ thống 4G core

Publié dans : Technologie
  • Soyez le premier à commenter

  • Soyez le premier à aimer ceci

Tối ưu hiệu năng đáp ứng các yêu cầu của hệ thống 4G core

  1. 1. Cloud for 4G Core 4G Core Introduction1 Performance Problems2 Next Plan3
  2. 2. 4G Core Network & NFV
  3. 3. OCS Requirement Average Latency < 2ms 200.000 Request per seconds 80M customers Hardware cost < 0.1$ /sub Uptime 99.999%
  4. 4. EPC Requirement Avarage Latency < 2ms >100k Request per seconds 1-2M customers Throughput: 300Gbs Offline tracing
  5. 5. Objective Cloud design Optimization & Simulation • VM design. • VN network Design • Compute. • Network. • Storage. • Software INPUT Bare metal design Requirements OUTPUT Number VM VM flavor & configuration VN configuration
  6. 6. Openstack for 4g core • Openstack: Queens • Hypervisor: KVM • Network: OpenvSwitch • Storage: CEPH • Hardware: x86_64 • OS: Redhat
  7. 7. 2.Performance Issues • Compute processing - CPU - Memory • Packet processing - Throughtput - Latency
  8. 8. Compute resources • High rate cpu usage - High cpu by workload(VM > Host 15%) • Competing for cpu resources - CPU Steal Time (%st)
  9. 9. Solution • CPU pinning: VM pinned to dedicated CPU cores - Numa - Hyperthreads - Hugepages
  10. 10. NUMA • NUMA awareness Scheduling - Non-Uniform Memory Access - Each CPU has it own memory(fast) - Other memory can accessed indirectly(slower)
  11. 11. HyperThreads • Hyper Threading • CPU Caching
  12. 12. Hugepages • Hugepages: - Allocate by NUMA - No swapping
  13. 13. Conclusion • Result: ~ 95% physical • Advantages: - Isolate VM resources - Optimal using resources% • Disadvantages: - Expensive - Inflexiable
  14. 14. Network Issues • Latency - Controller plane apps • Throughput - Data plane apps • Quality - Packet loss
  15. 15. OpenvSwitch • Multilayer virtual switch • Feature: VLAN, STP, LACP, Mirroring, Flow, Tunnel, QoS
  16. 16. OpenvSwitch Datapath • Datapath is the forwarding plane of OVS. - System datapath(default) - Userspace datapath(netdev-dpdk)
  17. 17. DPDK(Data Plane Development Kit) • DPDK: accelerate packet processing workloads running on a wide variety of CPU architectures EAL: Environment Abstraction Managing Queues: rte_ring Memory Management: rte_mempool Buffer Management: rte_mbuf Other Libraries
  18. 18. OVS-DPDK • Benefit: - Bypass kernel - Batch packets handling - …
  19. 19. OVS-DPDK • Additional: - Vhostuser - PMD Driver - PMD Thread - …
  20. 20. PMD Thread performance • PMD Threads: - Multi PMD threads - CPU pinning (Poll mode) - Use vhostuser multi queue Packet size 64 Physical NIC 10GB PMDs 4 Physical 15Mpps VM(Linux socket) 200Kpps Latency https://software.intel.com/content/www/us/en/develop/articles/configure-vhost-user-multiqueue-for-ovs-with- dpdk.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+ISNMain+%28Intel+Developer+Zone+Articles+Feed%29
  21. 21. Packet loss • Issue: - Packets loss while PMD threads low usage rate - VM process packet not fast enough • Solutions: - Increase tx/rx queues size - Using DPDK app in VM
  22. 22. Dataplane throughput • EPC throughput: 36Gbs/VM • OVS-DPDK: - Throughput not enough - Too many resources for OVS • Solution: - PCI Passthrough ??? - SR-IOV
  23. 23. SRIOV for Data plane • Physical Function • Virtual Function: - “lightweight” PCI Advantages: - Optimal resources - Minimize overhead, bottlenecks - DMA to VM memory http://www.intel.com/content/dam/doc/application-note/pci-sig-sr-iov-primer-sr-iov-technology-paper.pdf
  24. 24. PCI Locality Mapping • PCI map to NUMA • VM map to NUMA PCI and VM in same NUMA is better
  25. 25. 3. Plan OVS-DPDK Offload Smart NIC. SDN. Cloud for 5G. Container.
  26. 26. Thankyou!

×