I have a processing graph that reads from a Kafka queue (using reactive-kafka), do some processing and then write the results into another Kafka queue. I am trying to maximize the number of messages per seconds that flow though the graph and to that end would be very useful to know which one of the stages is the one that is limiting thoughtput.
Currently I am doing this by trial-and-error, for example I replace a stage in the graph with Sink.ignore and measure thoughtput, so for example I established that the source tops out at 50K msg/sec, when I add deserialization I slow-down to 25K msg/sec, and with processing and writing out to Kafka I get down to 12K msg/sec. but I was wondering whether there is a better way to detect dynamically which stage is applying backpressure. Thanks! -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
