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

no-jira: rate limiter now takes part in checkpoint #33

Merged
merged 1 commit into from
Aug 9, 2021

Conversation

swachter
Copy link
Contributor

@swachter swachter commented Aug 4, 2021

When running benchmarks with the direct runner checkpoints of the input are taken at regular intervals. The rate limiter state must also be part of that checkpoint in order to guarantee its rate-limiting behavior even in case of checkpoints.

@swachter swachter requested a review from fooker August 4, 2021 08:52
Comment on lines 49 to 51
public static State of(long currentTimeMillis, long flowsPerSecond) {
return new State(currentTimeMillis, flowsPerSecond);
}
Copy link
Member

Choose a reason for hiding this comment

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

What's the reason for these methods? They just copy the exact same parameters.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No specific reason. Just a matter of style.

Copy link
Member

Choose a reason for hiding this comment

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

Then we should not do it. It just increases brain load...

@swachter swachter merged commit 2556d41 into master Aug 9, 2021
@swachter swachter deleted the swachter/benchmark-fixup branch August 9, 2021 10:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants