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

Make the rate more predictable #25

Open
hariso opened this issue Sep 22, 2022 · 0 comments
Open

Make the rate more predictable #25

hariso opened this issue Sep 22, 2022 · 0 comments
Labels
feature New feature or request

Comments

@hariso
Copy link
Contributor

hariso commented Sep 22, 2022

Feature description

The current approach with read time won't exactly produce the number of messages per second. It will always sleep for the specified time before producing the record, regardless of how much time elapsed since the last time the connector produced a record. Using something like golang.org/x/time/rate would make this more accurate. Another improvement we could do if/when we have time.

-- @lovromazgon

@hariso hariso added feature New feature or request triage To be triaged labels Sep 22, 2022
@meroxa-machine meroxa-machine moved this to Triage in Conduit Main Sep 22, 2022
@lovromazgon lovromazgon removed the status in Conduit Main Oct 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
Status: No status
Development

No branches or pull requests

1 participant