Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

cmd-forwarder-vpp started reaching memory limits during basic, heal tests on packet with new VPP #332

Open
Bolodya1997 opened this issue Aug 30, 2021 · 1 comment
Open

cmd-forwarder-vpp started reaching memory limits during basic, heal tests on packet with new VPP #332

Bolodya1997 opened this issue Aug 30, 2021 · 1 comment
Assignees
@denis-tingaikin
Labels
bug Something isn't working performance The problem related to system effectivity

Comments

@Bolodya1997
Copy link

Bolodya1997 commented Aug 30, 2021 •
edited
Loading

Expected Behavior

cmd-forwarder-vpp shouldn't reach memory limit during tests.

Current Behavior

cmd-forwarder-vpp reaches current memory limit (400Mi) during basic, heal tests on packet after VPP upgrade.

Steps to Reproduce

Run basic, heal tests on packet.

Context

Tested on deployments commits:

  • with old VPP : ce003f5d821c761aaafd195cf51e8b359a6652d3
  • with new VPP : 692b0865a7ea7dda5f6ab31e1490169f8f142dae
@Bolodya1997 Bolodya1997 added the bug Something isn't working label Aug 30, 2021
@Bolodya1997 Bolodya1997 changed the title cmd-forwarder-vpp reaches memory limits during basic, heal tests on packet cmd-forwarder-vpp started reaching memory limits during basic, heal tests on packet with new VPP Aug 30, 2021
@Bolodya1997 Bolodya1997 mentioned this issue Aug 30, 2021
Merged
@denis-tingaikin denis-tingaikin added the performance The problem related to system effectivity label Sep 7, 2021
@denis-tingaikin denis-tingaikin self-assigned this Nov 17, 2021
@denis-tingaikin
Copy link
Member

denis-tingaikin commented Nov 23, 2021 •
edited
Loading

@edwarnicke This is not reproducing with networkservicemesh/deployments-k8s#2793

I think we need to consider why do we need now 500Mi after release.

@zolug zolug mentioned this issue Mar 16, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@denis-tingaikin denis-tingaikin

Labels
bug Something isn't working performance The problem related to system effectivity
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Bolodya1997 @denis-tingaikin