Raise loop and chunk limit for newer kernels by benkilimnik · Pull Request #1795

Raise loop and chunk limit for newer kernels by benkilimnik · Pull Request #1795 · pixie-io/pixie

Signed-off-by: Benjamin Kilimnik <bkilimnik@pixielabs.ai>

benkilimnik changed the title ~~Raise loop and chunk limit for kernels >5.1 by 21x~~ Raise loop and chunk limit for kernels >5.1

Dec 6, 2023

benkilimnik changed the title ~~Raise loop and chunk limit for kernels >5.1~~ Raise loop and chunk limit for newer kernels

Dec 6, 2023

Signed-off-by: Benjamin Kilimnik <bkilimnik@pixielabs.ai>

Signed-off-by: Benjamin Kilimnik <bkilimnik@pixielabs.ai>

Signed-off-by: Benjamin Kilimnik <bkilimnik@pixielabs.ai>

etep approved these changes Jan 18, 2024

ddelnano pushed a commit to k8sstormcenter/pixie that referenced this pull request

Feb 25, 2026

Summary: Dynamically increase the loop limit for newer kernels with
higher instruction limits (1 million for kernels > 5.1) by 21x to reduce
data loss and raise ingest. More details in pixie-io#1755.

One open question is whether we want to add vizier flag to toggle this
behavior in case there are unforseen performance bottlenecks for certain
clusters.

Type of change: /kind feature

Test Plan: Existing targets + perf/demo tests outlined in pixie-io#1755.

---------

Signed-off-by: Benjamin Kilimnik <bkilimnik@pixielabs.ai>

ddelnano pushed a commit to k8sstormcenter/pixie that referenced this pull request

Feb 25, 2026

Summary: Dynamically increase the loop limit for newer kernels with
higher instruction limits (1 million for kernels > 5.1) by 21x to reduce
data loss and raise ingest. More details in pixie-io#1755.

One open question is whether we want to add vizier flag to toggle this
behavior in case there are unforseen performance bottlenecks for certain
clusters.

Type of change: /kind feature

Test Plan: Existing targets + perf/demo tests outlined in pixie-io#1755.

---------

Signed-off-by: Benjamin Kilimnik <bkilimnik@pixielabs.ai>