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

Throughput Control #2512

Closed
galibey opened this issue Jul 28, 2022 · 2 comments
Closed

Throughput Control #2512

galibey opened this issue Jul 28, 2022 · 2 comments
Assignees
Labels
Milestone

Comments

@galibey
Copy link
Contributor

galibey commented Jul 28, 2022

We need to find a way to control the throughput that we produce during integration testing. Currently, it is limited only by available system resources and is unstable due to that fact.

We need to figure out on which level we want to do this. Possible options: fluvio-test where we generate the test data or fluvio client where we can add a back pressure mechanism to control the throughput that goes to the Producer.

@tjtelan
Copy link
Contributor

tjtelan commented Jul 28, 2022

I vote for adding this in fluvio, and adding a fluvio-test test to externally verify the throughput based on client configuration.

Users would want this, and it would be nice to separate our need for client back pressure support from fluvio-test.

@tjtelan tjtelan added the good first issue Good for newcomers label Jul 28, 2022
@sehz
Copy link
Contributor

sehz commented Jul 29, 2022

We need to fix this ASAP with CI becoming more flaky

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants