-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Optimize Kafka IO: Remove Guava Stopwatch overhead from consumer.poll() loop #37705
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
Open
junaiddshaukat
wants to merge
1
commit into
apache:master
Choose a base branch
from
junaiddshaukat:remove-kafka-stopwatch-overhead
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
The TODO is still valid. It's referring to Kafka metrics: https://kafka.apache.org/20/generated/consumer_metrics.html
Stopwatch and System.currentTimeMillis doesn't make a difference here
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.
Thanks for the clarification, and I think there was some misunderstanding on my side about the intent of the TODO.
I originally read
as “the custom Stopwatch‑based timer in the hot consumer.poll() loop is too expensive and should be removed / replaced,” so I focused this PR on changing how we measure the latency (from Stopwatch to System.currentTimeMillis) while keeping the existing Beam metric behavior.
From your comments and the link to the Kafka consumer metrics docs, I now understand that your intent is more about relying on Kafka’s own fetch-latency-avg JMX metric instead of having a separate Beam RpcLatency metric here, rather than just which Java clock is used. In that sense, you’re right: this PR doesn’t actually implement the TODO, it just refactors the timer and doesn’t add much value.
Given that, I’m happy to either:
Please let me know which direction you’d prefer; if you’d rather keep the current behavior and leave the TODO for later, I’ll go ahead and close this PR.