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

feat(ebpf): configurable pipeline channel size #4182

Merged

Conversation

NDStrahilevitz
Copy link
Collaborator

1. Explain what the PR does

236d33e feat(ebpf): configurable pipeline channel size

236d33e feat(ebpf): configurable pipeline channel size

Allow configuring the event channels in pipeline stages using the
`pipeline-channel-size` flag and config entry. Rigorous testing of the
effect of playing with this value has yet to be done, so the default
value is currently 10000 as hardcoded before.

Tentatitevely, reducing the size of this configuration value may help
reduce the mean memory usage, perhaps reduce channel contention, but may
be at the cost of a greater risk for event loss.

2. Explain how to test it

  1. tracee --pipeline-channel-size X
  2. Configure in a config file with pipeline-channel-size: X at the root level

3. Other comments

Copy link
Member

@geyslan geyslan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

The failing integration seems related to capture.

10000,
"<size>\t\t\t\tSize, in event objects, of each pipeline stage's output channel",
)
err = viper.BindPFlag("blob-perf-buffer-size", rootCmd.Flags().Lookup("blob-perf-buffer-size"))
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

blob-perf-buffer-size? shouldn't this be pipeline-channel-size?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should be.

Allow configuring the event channels in pipeline stages using the
`pipeline-channel-size` flag and config entry. Rigorous testing of the
effect of playing with this value has yet to be done, so the default
value is currently 10000 as hardcoded before.

Tentatitevely, reducing the size of this configuration value may help
reduce the mean memory usage, perhaps reduce channel contention, but may
be at the cost of a greater risk for event loss.
@NDStrahilevitz NDStrahilevitz merged commit d133ae2 into aquasecurity:main Jul 16, 2024
32 checks passed
@NDStrahilevitz NDStrahilevitz deleted the pipeline_size_config branch July 16, 2024 10:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants