-
Notifications
You must be signed in to change notification settings - Fork 119
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
Problem with latency #540
Comments
@sknot-rh @ppatierno Any ideas? |
Hi. Are you sure you do use bridge just as a producer? I did some testing and when the bridge is just producing records, it won't get over 54 threads. |
Sure. The current instance is only used to produce messages |
@Arfey I am going to close this issue, not hearing from you since years. Feel free to re-open if the problem seems to be still in place for you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi ✋
The vast majority of kafka bridge requests have good response times (less than 200ms), but some have more than 2-5 seconds. I tried to find the problem and check the latency from the pod for the
/ready
handler (to rule out kafka and networking issues), but also some requests had response times more than 1-2 seconds.Without a load, this problem is not present (produce 2-3 messages per second).
i guess i have not problem with gc or heap (even when i increase the memory it does not give any result). Also i have not problem with cpu:
i have discover problem (1-3%) with throttling and increase count of cores for bridge from 1 to 4 (throttling 0%) and it have decreased some count of slow requests but not fully solved my problem
Someone knows what might be wrong or how i can solve a current problem? Thx!
The text was updated successfully, but these errors were encountered: