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

Determine Mizar eBPF resource requirements on per-Pod and per-Cluster Node basis #617

Open
vinaykul opened this issue Feb 7, 2022 · 0 comments
Assignees

Comments

@vinaykul
Copy link
Member

vinaykul commented Feb 7, 2022

What would you like to be added:

  1. Determine memory footprint of eBPF map entries used on per-Pod basis (without network policy support). Itemize by memory requirements for egress packet handling, bouncer entry, and ingress handling.
  2. Determine minimum Divider and Bouncer memory footprint requirements assuming a cluster with 1 divider and 1 bouncer.
  3. Determine memory footprint of eBPF map entries used on per-Service (without network policy support). Itemize by memory requirements for egress packet handling, bouncer entry, and ingress handling.

Why is this needed: This is needed to determine the resource requirements and get a sense of how Mizar will scale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants