From ce9ab72e4809661413bc0b73396d13be42b843f0 Mon Sep 17 00:00:00 2001 From: Ali Behjati Date: Thu, 11 Apr 2024 12:15:14 +0200 Subject: [PATCH] chore: update Pythnet sample config (#113) 100ms notify_sched_interval is causing problems for the publishers and this change reverts it back to 400ms. The exact reason for the problem is still unknown but we think their slow clients (forked from our example publisher) and poor agent design cause this issue. A major refactor is going to improve agent bottlenecks and also remove notifications to make sure it doesn't add unnecessary overhead to the clients. --- config/config.sample.pythnet.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config/config.sample.pythnet.toml b/config/config.sample.pythnet.toml index 48205b8..d371262 100644 --- a/config/config.sample.pythnet.toml +++ b/config/config.sample.pythnet.toml @@ -69,4 +69,4 @@ exporter.maximum_compute_unit_price_micro_lamports = 100000 # The duration of the interval at which `notify_price_sched` notifications will be sent. # Note that this doesn't affect the rate at which transactions are published: # this is soley a backwards-compatibility API feature. -notify_price_sched_interval_duration = "100ms" +notify_price_sched_interval_duration = "400ms"