Drab is slow in production

Sounds like Heroku is adding latency. Do you have a URL to your test instance so I can trace the network connection?

It may make sense that the latency of the network increase time from one to five seconds.

@wlminimal, can you measure how long this single poke takes in dev and prod? Just measure the time difference:

IO.puts(" ++++++++++++ poking +++++++++++++")
t0 = :os.system_time(:milli_seconds)
poke(socket,
  total_sent: total_sent,
  deilvered_count: deilvered_count,
  undelivered_count: undelivered_count,
  total_clicks: total_clicks
)
IO.puts("+++++++++++++ poking is done ++++++++++")
IO.puts("it took #{:os.system_time(:milli_seconds) - t0} ms")

I tried..
in dev it took 2031 ms
in prod it took 8691 ms.

umm. I really want to do it
But my problem is in logged in dashboard.
I don’t know the way to show you :(

What is your latency to your heroku server? Like just access a path that doesn’t exist on it and how long does it take to respond 404 from that request?

EDIT: For note, Drab works over Phoenix Channels, it would absolutely not be slow, either the work being done is slow or the network connection is slow.

few seconds, 1 or less

tried this https://www.texty.marketing/non-exist

OMG. 2 seconds on DEV? It is definitely not a problem with latency, but with the complexity of your page! Either you page renders for 2 seconds, or you have a plenty of big assigns on the page.

I suggest two solutions for this:

• cut your page into pieces by using partials - here you can see the advantage of this approach
• do not use Drab.Live, as it must re-render the page at every poke you do; use Drab.Element to update the page instead

I figured that would just be from the HTTP request the server makes to that other server they mentioned earlier?

This 2 seconds is just a poke. What poke does is:

• get the current assign values from the browser (it can be a long operation if you have a lot of big assigns); it is cached later
• re-render the page, which also can be a long operation if the page is big

Oh wait that’s from the server to the client with response back to server (not client to server with response back to client)? That is crazy slow then, I’ve never seen that be slow in dev! (I use a lot of shared commanders though)