Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1soppk-00E9hy-0c for pgsql-general@arkaria.postgresql.org; Thu, 12 Sep 2024 19:50:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sopol-00FzGm-Lj for pgsql-general@arkaria.postgresql.org; Thu, 12 Sep 2024 19:49:27 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sopol-00FzGc-Ab for pgsql-general@lists.postgresql.org; Thu, 12 Sep 2024 19:49:27 +0000 Received: from mail-lf1-x12a.google.com ([2a00:1450:4864:20::12a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sopoh-000rph-C6 for pgsql-general@lists.postgresql.org; Thu, 12 Sep 2024 19:49:26 +0000 Received: by mail-lf1-x12a.google.com with SMTP id 2adb3069b0e04-5365b6bd901so1617541e87.2 for ; Thu, 12 Sep 2024 12:49:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1726170563; x=1726775363; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=WuWKZj31WtNBRzjX4VeXJ01NttEC0U0TVhdSe4vqLAU=; b=iAiERZ6JlvzxsZox31HKRHuiL7GlFtN/sZl/zJ6tD3kHZVdPfeEdz8cL4WEovO4ies 1veQkrPVt7ix6yvhe44D9VTjNy/+KiEx4SaFgx6rb/3N49O/Ii2Xb4F8gMpI6ImQpr13 2IL7LWZZebpqQE43DB9QQkE3Lrlxm9IPVGaX/zKaBFaLBav7dS080Gpgf1pXeti5ro3J Ee28iwfIxIYqFv3EAxOAcnjLyjeN7vGyZidOiA1zW3x0nuKY/ByzlnvECqoFtUUscDHI yY+sQ82ifE3KKmF0PvoBbBoZ2QWO8FzZS5lkU0x3HM3H1j2Wz3kP/CG5abH4T2bOB8ST BOCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726170563; x=1726775363; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=WuWKZj31WtNBRzjX4VeXJ01NttEC0U0TVhdSe4vqLAU=; b=RB9rGdX5ibgR/HRpUIw93cWgxii7MYuWOd+n89rXq7qOnMq1/uZWMik7OBo+AGxBfb +oJKaT3kvZGtTGPgNcfdQovzdyw6bigwuqyBkGwP/UcYpsfrcXDxtpY/wJ8bMMMCmdtU qeWr9JrhyuIp/x9vdvhH/GJR435A6JWcvcUPn88tHJOWiDT4qnafeTV+EEsHy/iYkp9K IcXPo9HAzmilsJtG1v6qBiSdynXBhuf0ByBZ2ICJowUMqVgv1/W9IoTMGGBfCpGTl5gk nF71liAhwV9ZQvBH7V/cdQEpobC9ZoZD9tTWMWM1ZovPjXV+vBZMTK2ERS8ep6cAKqYt IBiw== X-Gm-Message-State: AOJu0Ywn3F8eHlqlUlmttNFggtroea8vq9WrsCDHAYMgv84jBn82pPYy igt53CfcnIyKYD/4L6uKcusvw2Jbuhr+rTpvS0zONaNKtn04E6LJ4esyjRjkqoGgiKdt1HLb7sL 3YPCZ+P6YD4z7Qzrnl93DTslDBsFnFQt2eQffvQ== X-Google-Smtp-Source: AGHT+IFKKqJoxmM28JjeG9ZrU4ctqocqduTLpCOoV8sJzDV+IED4Xpq+qpypnTsFSFOUKH14DsZ9K6rf1UuT+oQ2Iik= X-Received: by 2002:a05:6512:3195:b0:530:aa4b:81c7 with SMTP id 2adb3069b0e04-53678ff4d82mr2619254e87.59.1726170562557; Thu, 12 Sep 2024 12:49:22 -0700 (PDT) MIME-Version: 1.0 From: Durgamahesh Manne Date: Fri, 13 Sep 2024 01:21:55 +0530 Message-ID: Subject: Recommendations on Improving the debezium performance even on medium workload To: pgsql-general@lists.postgresql.org, pgsql-in-general@postgresql.org, Greg Sabino Mullane , "kdg.dev@gmail.com" Content-Type: multipart/alternative; boundary="0000000000003405560621f1671d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000003405560621f1671d Content-Type: text/plain; charset="UTF-8" Hi Team How do we improve the debezium performance? Recommendations at kafka configuration side Agenda is to minimize the lag during moderate or high work load on db default > poll.interval.ms = 500ms Recommended value for balanced performance > 1000ms Recommended value for high throughput > 1000ms to 5000ms default > max.batch.size = 2048 allocated > 2560 Recommended value for balanced performance > 500 to 1000 Recommended value for high throughput > 2000 or 5000 default > max.queue.size = 8192 allocated > 10000 Recommended value for balanced performance > 7500 (1000 to 10000) Recommended value for high throughput > 10000 based on kafka load we can optimize debezium connector performance default > heartbeat.interval.ms = 0 allocated > 5000ms Recommended value for this > 5000ms to 10000ms Are these helpful ? Need auto connectivity even on connector(slot) failure please let me know your recommendations please Regards, Durga Mahesh --0000000000003405560621f1671d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Team=C2=A0

How do we improve=C2=A0th= e debezium performance?
Recommendations at kafka configuration si= de
Agenda is to minimize the lag during moderate or high work loa= d on db=C2=A0

<= p>default > poll.interval.ms =3D= 500ms=C2=A0
Recommended value for balanced performance > 1000ms
Recommended value for high throughput > 1000ms to 5000ms

=C2=A0

=C2=A0

default > max.batch.size =3D 2048 allocated > 2560 Recommended value for balanced performance > 500 to 1000
Recommended value for high throughput > 2000 or 5000

=C2=A0

= default > max.queue.size =3D 8192 allocated > 10000
Recommended value for balanced performance > 7500 (1000 to 10000)
Recommended value for high throughput > 10000

based on kafka load = we can optimize debezium connector performance=C2=A0

=C2=A0

def= ault > heartbeat.interval.ms =3D 0 allocated > 5000ms
Recommended value for this > 5000ms to 10000ms


Are thes= e helpful=C2=A0 ?

Need auto connectivity even on connector(slot) fail= ure=C2=A0

please=C2=A0let=C2=A0me know your recommendations please=C2= =A0


Regards,

Durga Mahesh

--0000000000003405560621f1671d--