From 6243d0cf10f9ff6f66634a7fa06e280f40d49293 Mon Sep 17 00:00:00 2001 From: Gabriel Oliveira Date: Thu, 18 Jul 2024 18:17:17 -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 | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/lib/broadway_kafka/producer.ex b/lib/broadway_kafka/producer.ex index 63c1908..0758920 100644 --- a/lib/broadway_kafka/producer.ex +++ b/lib/broadway_kafka/producer.ex @@ -225,9 +225,10 @@ defmodule BroadwayKafka.Producer do 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 - the shared_client resource usage gains. + To mitigate this, you can split your topics between multiple pipelines, but notice that this will + increase the resource usage as well. By creating one new client/connection for each pipeline, + you effectively diminishing the `shared_client` resource usage gains. So make sure to measure + if you enable this option. """ use GenStage