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.

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

CPU near 100% -> packet loss? #277

Open
tortoisedoc opened this issue Oct 2, 2021 · 0 comments
Open

CPU near 100% -> packet loss? #277

tortoisedoc opened this issue Oct 2, 2021 · 0 comments
Labels
help wanted Extra attention is needed libslirp

Comments

@tortoisedoc
Copy link

tortoisedoc commented Oct 2, 2021

Setup:

  • 3 separate physical servers setup, connected via Wireguard on internal network
    Problem:
    We have noticed that on high load (during performance testing), the slirp4netns nears 100% CPU (expected).
    This however seems to cause packet loss, and consenquent timeouts at HTTP level (for example to kubernetes control node).
    The configuration is the one from usernetes (i.e. no new options added, neither old removed).
  • is there ways to improve slirp4netns performance (i.e. by scaling out to more CPU cores)
  • is there means for us to investigate more?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed libslirp
Projects
None yet
Development

No branches or pull requests

2 participants