CS 4.22.0 VPC vRouter Performance and crash, no ROUTED on ROUTED setting Only
- Lingua principale
- Java
- Stelle
- 3.1k
- Fork
- 1.4k
- Merge medio
- 6g 19h
- PR unite (30g)
- 32
Descrizione
### problem
Using CS4.22.0 VPC vRouter - Routed scenario, using above 2CPUs and 2GiB RAM, performance is not increased, we noticed similar behavior on NAT'ed VPCs also: no Load balancer or other features besides the custom ACLs.
Using as router only with the BGP up, I created a 4CPU and 4G vRouter and a 8CPU and 8GvRouter, the performance does not improve on throughput is seems it reaches about 800Gbps and stop there, and sometimes traffic freezes, and many times using pipe commands make the vRouter to crash.
**This performance issue is not observed on the same configuration on Isolated Networks.** where we reached 5Gbps to the VM.
### versions
CS 4.22.0 with 1:1 oversubscription - no Oversubscription on CPU neither on memory
Host Ubuntu 22.4 KVM
### The steps to reproduce the bug
1. Create a routed VPC - Dynamic routing
2. use a Network Offering with 8CPU and 8GiB RAM
3. Create the custom ACL's
4. Apply, and Crete a VM
5. Test using a massive file ...
### What to do about it?
This Issue is observed on VPCs only, and is more noticeable on Routed VPCs-
Important the same test on Isolated NAT networks have no issues, we reached 5Gbps, with complex firewall configurations.
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia riproducendo lo scenario di VPC instradata con il 8-CPU/8-GiB Network Offering indicato, ACLs personalizzate, BGP e una VM, quindi confronta il throughput con quello di una rete isolata. Verifica se il ridimensionamento delle risorse di vRouter modifica il throughput e se pipe commands causano blocchi o crash; il lavoro è completo quando la VPC instradata non presenta più il limite di prestazioni né crash.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- ubuntu
- Ambito
- cloud, infrastructure, networking
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Tranquilla
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 42/100