apache / apache/cloudstack

CS 4.22.0 VPC vRouter Performance and crash, no ROUTED on ROUTED setting Only

Abierto
#13,267 6 comentarios 0 reacciones 0 asignados Ver en GitHub
status:needs-investigation type:performance
Lenguaje dominante
Java
Estrellas
3.1k
Forks
1.4k
Merge medio
6 d 19 h
PR fusionados (30 d)
32

Descripción

### 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.

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Comienza reproduciendo el escenario de VPC enrutada con el 8-CPU/8-GiB Network Offering indicado, ACLs personalizadas, BGP y una VM; después, compara el rendimiento con el de una red aislada. Comprueba si escalar los recursos de vRouter cambia el rendimiento y si pipe commands provocan bloqueos o crashes; se considera terminado cuando la VPC enrutada ya no presenta el límite de rendimiento ni crashes.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
ubuntu
Área
cloud, infrastructure, networking
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Tranquilo
Claridad
Bastante claro
Aptitud para principiantes
42/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.