You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are experiencing significant latency issues with our Elixir application deployed on Fly.io, particularly when deploying across multiple regions (Frankfurt and London) with Kanta activated. The response time deteriorates from 0.2 seconds to more than 5 seconds under these conditions.
Configuration Details
Below are the relevant parts of our configuration, highlighting the setup for Kanta and the application's supervision tree.
def start(_type, _args) do
children = [
....
{Kanta, Application.fetch_env!(:nexus, Kanta)},
...
]
opts = [strategy: :one_for_one, name: Nexus.Supervisor]
Supervisor.start_link(children, opts)
end
lib/nexus_web/gettext
defmodule NexusWeb.Gettext do
use Gettext,
otp_app: :nexus,
repo: Application.compile_env(:nexus, :gettext_repo)
end
Additional Information
This issue might be related to Fly.Postgres, considering the multi-region deployment aspect.
We have not observed any relevant logs that directly point to the cause of the latency.
Do you know what the exact problem might be and what could we do to try and find a solution?
thanks.
The text was updated successfully, but these errors were encountered:
We are experiencing significant latency issues with our Elixir application deployed on Fly.io, particularly when deploying across multiple regions (Frankfurt and London) with Kanta activated. The response time deteriorates from 0.2 seconds to more than 5 seconds under these conditions.
Configuration Details
Below are the relevant parts of our configuration, highlighting the setup for Kanta and the application's supervision tree.
Here is my configuration:
config.exs
prod.exs
application.ex
lib/nexus_web/gettext
Additional Information
This issue might be related to Fly.Postgres, considering the multi-region deployment aspect.
We have not observed any relevant logs that directly point to the cause of the latency.
Do you know what the exact problem might be and what could we do to try and find a solution?
thanks.
The text was updated successfully, but these errors were encountered: