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

Investigate high latency ingestion #54

Closed
raminqaf opened this issue Aug 11, 2022 · 4 comments
Closed

Investigate high latency ingestion #54

raminqaf opened this issue Aug 11, 2022 · 4 comments
Assignees
Labels
area/e2eTest Relates to e2e tests component/mirror type/question Further information is requested

Comments

@raminqaf
Copy link
Contributor

After upgrading Kafka to 3.1, the ingestion time increased noticeably. I had to add sleeps in the e2e tests after each ingest. We should investigate what the main reason is.

@raminqaf raminqaf added type/question Further information is requested area/e2eTest Relates to e2e tests component/mirror labels Aug 11, 2022
@torbsto torbsto added this to the Kafka 3.0+ support milestone Aug 11, 2022
@torbsto torbsto added this to Quick Aug 11, 2022
@torbsto torbsto moved this to Todo in Quick Sep 6, 2022
@DawidNiezgodka DawidNiezgodka self-assigned this Sep 15, 2022
@DawidNiezgodka
Copy link
Contributor

Results

@raminqaf raminqaf moved this from Todo to In-Review in Quick Sep 21, 2022
@raminqaf raminqaf moved this from In-Review to In Progress in Quick Sep 21, 2022
@DawidNiezgodka
Copy link
Contributor

The second part of the test involves testing the consumption time, that is, we want to measure how much time a consumer needs to read all records send by the ingest service to a specific kafka topic.

@DawidNiezgodka DawidNiezgodka moved this from In Progress to In-Review in Quick Sep 29, 2022
@DawidNiezgodka
Copy link
Contributor

@DawidNiezgodka
Copy link
Contributor

Hypothesis: Kafka 3 needs more time for the stuff around producer and consumer (de)activation. When they are already active, then the processing is faster than Kafka 2. One of the solution to the problem could be to add additional resources to speed up the start-up.

Repository owner moved this from In-Review to Done in Quick Oct 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/e2eTest Relates to e2e tests component/mirror type/question Further information is requested
Projects
Status: Done
Development

No branches or pull requests

3 participants