-
Notifications
You must be signed in to change notification settings - Fork 474
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
[CHORE] processing discovered targets async #3517
[CHORE] processing discovered targets async #3517
Conversation
b8ea4df
to
d219c9d
Compare
I think tests are failing because master is failing as well, but I'm not sure. |
This comment was marked as spam.
This comment was marked as spam.
@janumpallykalyan your last comment is broken |
…v.valueFrom)" (open-telemetry#3510) * Revert "Support configuring java runtime from configmap or secret (env.valueF…" This reverts commit 2b36f0d. * chlog (open-telemetry#3511)
d219c9d
to
42eec92
Compare
This comment was marked as spam.
This comment was marked as spam.
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.
I like the idea of these changes! I've left some questions and comments about the specifics.
More generally, since we're changing the execution model of the Discoverer, I'd love to see a few more unit tests verifying if the triggers work correctly. Also, comments for all the new functions, explaining what purpose they serve in the new design.
Signed-off-by: Nicolas Takashi <[email protected]>
Signed-off-by: Nicolas Takashi <[email protected]>
Signed-off-by: Nicolas Takashi <[email protected]>
Signed-off-by: Nicolas Takashi <[email protected]>
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 to me overall, some final nitpicks. Could you also rerun the benchmark to see if the concurrency changes affected performance?
Co-authored-by: Mikołaj Świątek <[email protected]>
Bench results after lock per job |
Signed-off-by: Nicolas Takashi <[email protected]>
Signed-off-by: Nicolas Takashi <[email protected]>
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.
Thank you for taking this up!
@nicolastakashi Shoudl we expect that in large environments that the CPU usage of the |
Yes, this is due to the amount of go routines. |
Description:
This change addresses issue #3512. The implementation is inspired by the Prometheus Scrape Manager, as referenced in the source code here: Prometheus Scrape Manager.
Below are the
benchstat
results comparing the currentmain
branch with the proposed changes in this PR. These results highlight the performance improvements and trade-offs introduced by this update.Link to tracking Issue(s):
Testing: Run Unit Tests and BenchMarch Tests
Documentation: N/A