-
Notifications
You must be signed in to change notification settings - Fork 10
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
Close probes concurrently #212
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Can you share some benchmarks?
Yes, I needed a separate performance fix in order to properly benchmark this, so both tests are being performed based off that branch. Methodology: I'm running the CO-RE test suite (we have three suites, so the true number is roughly this times 3)
Without this PR: Runs CO-RE test suite in |
/merge |
Devflow running:
|
ea577da
to
7c888e1
Compare
/merge |
Devflow running:
|
/remove |
Devflow running:
|
/merge |
Devflow running:
|
What does this PR do?
Modifies the
(*Manager) Close()
method to close the probes concurrently.Motivation
The Networks team has dozens of kprobes and each one takes 30-50ms to call the close() syscall on the perf_kprobe PMU, which adds up to an extra second of time on each test. We set up and tear down the tracer entirely for each test, which across all our tests, adds up to minutes of test time.
Additional Notes
Describe how to test your changes
CI passes here showing KMT was all green: DataDog/datadog-agent#33054