Replies: 1 comment 1 reply
-
It would be very difficult for anybody to help you with this issue with just static information; you will need to examine logs and also profile your application to see where the bottlenecks are. Not relevant to your problem, but this is wrong The |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am new to Kafka and I am implementing a spring boot application with a SOAP web service to replace an old ESB. When testing the configuration with a single message and having the consumer reply in less than 10ms, messages from the producer and the consumer flow very quickly and the service replies with no problem. Running a load test with SOAPUI scales very quickly and I can run a test with 50 to 70 threads with no problem, the average response time is maintained in about 10 to 20ms. The problem I am having is when the consumer reply is delay for about 250ms (This is a requirement I have in my legacy system), testing with a single message works great and the flow from the producer to the consumer and back goes quickly and the service replies in about 280ms (This is an acceptable response for my configuration)). Things change when running a load test with SOAPUI. The test runs with about 20 threads, The SOAP service receives the request and then send them to the consumer using Kafka. The consumer receives the request very quickly and process them in about 250ms average. Then it send the reply back to the producer using a reply topic. The problem I have is that it takes the producer about 600ms or more to read the reply back from the consumer and the complete loop takes about 900 - 1200ms in average, which is way too high. I need some help trying to find out why the producer takes this extremely long time to read a reply that is already in the reply topic. trying to scale the solution is a complete failure and increasing the threads only makes things worse and the average response time keeps increasing when adding more threads, even adding more partitions to the topic or/and adding more consumers does not help the problem as the solution with this configuration will not scale. I am not sure if I am missing some configuration on the producer or the server. Any help is greatly appreciated.
This is the consumer and producer code
Beta Was this translation helpful? Give feedback.
All reactions