From 273763fd7379fdecaf4401da01ef14492db80cb9 Mon Sep 17 00:00:00 2001 From: Gabriel Oliveira Date: Thu, 18 Jul 2024 18:16:52 -0300 Subject: [PATCH] Update lib/broadway_kafka/producer.ex MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: José Valim --- lib/broadway_kafka/producer.ex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/broadway_kafka/producer.ex b/lib/broadway_kafka/producer.ex index 37c2529..63c1908 100644 --- a/lib/broadway_kafka/producer.ex +++ b/lib/broadway_kafka/producer.ex @@ -222,8 +222,8 @@ defmodule BroadwayKafka.Producer do Enabling shared client may drastically decrease performance. Since connection is handled by a single process, producers may block each other waiting for the client response. - This is more likely to be an issue if the producers on your pipeline are fetching message from multiple topics - and specially if there are very low traffic topics in the mix because of batch wait times. + This is more likely to be an issue if the producers on your pipeline are fetching message from + multiple topics and specially if there are very low traffic topics, which may block on batch wait times. In summary to mitigate this you can split your topics between multiple pipelines, but notice that this will increase the resource usage as well creating one new client/connection for each pipeline effectively diminishing