Skip to content

KAFKA-19370: Create JMH benchmark for share group assignor #19907

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

Merged
merged 1 commit into from
Jun 6, 2025

Conversation

AndrewJSchofield
Copy link
Member

@AndrewJSchofield AndrewJSchofield commented Jun 5, 2025

As part of readying share groups for production, we want to ensure that
the performance of the server-side assignor is optimal. In common with
consumer group assignors, a JMH benchmark is used for the analysis.

Reviewers: Apoorv Mittal apoorvmittal10@gmail.com

Copy link
Contributor

@apoorvmittal10 apoorvmittal10 left a comment

Choose a reason for hiding this comment

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

Thanks for the PR, LGTM.


private GroupSpec groupSpec;

private List<String> allTopicNames = Collections.emptyList();
Copy link
Contributor

Choose a reason for hiding this comment

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

Shouldn't it be as below, allTopicNames is changed later?

Suggested change
private List<String> allTopicNames = Collections.emptyList();
private List<String> allTopicNames = new ArrayList<>();

Copy link
Member Author

Choose a reason for hiding this comment

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

It works because this variable is overwritten with a new list created by AssignorBenchmarkUtils.createTopicNames.

@AndrewJSchofield AndrewJSchofield merged commit 5cf8b2a into apache:trunk Jun 6, 2025
28 checks passed
@AndrewJSchofield AndrewJSchofield deleted the KAFKA-19370 branch June 6, 2025 07:29
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.

2 participants