apache / apache/cloudstack

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

Aberta
#13,267 6 comentários 0 reações 0 responsáveis Ver no GitHub
status:needs-investigation type:performance
Linguagem predominante
Java
Estrelas
3.1k
Forks
1.4k
Merge médio
6d 19h
PRs com merge (30d)
32

Descrição

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

Guia de contribuição

Abrir o guia de contribuição

Direção de pesquisa

Comece reproduzindo o cenário de VPC roteada com o 8-CPU/8-GiB Network Offering listado, ACLs personalizadas, BGP e uma VM; em seguida, compare o throughput com o de uma rede isolada. Verifique se o escalonamento dos recursos de vRouter altera o throughput e se pipe commands causam travamentos ou crashes; considera-se concluído quando a VPC roteada não apresentar mais o limite de desempenho nem crashes.

Escrita pelo modelo de indexação a partir do texto da issue.

Avaliação

Stack de tecnologia
ubuntu
Domínio
cloud, infrastructure, networking
Tipo de issue
Bug
Dificuldade
4/5
Tempo estimado
3-5 dias
Status de atividade
Pouca atividade
Clareza
Razoavelmente clara
Facilidade para iniciantes
42/100

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.