mekusigjinn

mekusigjinn

I have a question regarding polling strategies.

I generally like doing GenServer + Process.send_after because it’s more intuitive for me.

Lately I came across two Internet sources that do this:

defmodule Example.BitcoinPriceUpdater do
  use Task
  def start_link(_arg) do
    Task.start_link(&poll/0)
  end
  def poll() do
    receive do
    after
      60_000 ->
        get_price()
        poll()
    end
  end
  defp get_price() do
    # Call API & Persist
    IO.puts "To the moon!"
  end
end

(excerpt: https://medium.com/@efexen/periodic-tasks-with-elixir-5d9050bcbdb3)

And also the same usage in JokenJwks library:

      use Task, restart: :transient
...
      @doc false
      def poll(opts) do
        interval = opts[:time_interval]

        receive do
        after
          interval ->
            _ = check_fetch(opts)
            poll(opts)
        end
      end

Is there any "gotcha"s when you use Task-based polling under Supervisor?

Specifically, at work I had the JokenJwks.DefaultStrategyTemplate used (via use) in my Phoenix application, but I was able to crash the module based Task when I ran a custom Mix Task, while the app was running.

The custom Mix Task did not even remotely use the same code base.
Setting :logger config to:

config :logger,
  level: :debug,
  handle_sasl_reports: true

Allowed me to see that when the process crashed, resources were:

  • Heap Size: 29_000
  • Reduction was around 440_000. Isn’t that pretty high? I still don’t know how to guage reduction units..

When I do a Process.monitor() + receive, I get instantaneous DOWN messages, so I am even more puzzled.

Frankly, I can’t quite grasp how a recursing poll() in a use Task, under Supervisor would be running - so is this like a long-running process?

Now if we talk about doing a GenServer + polling via recursive Process.send_after, I totally get that right off the bat - I know what’s happening.

So I wanted to ask - is there a case where one would want to use receive + after polling with use Task? Besides the fact that it might look “simpler”, especially when the intention is for a long-running poll?

Thanks in advance.

Showing Posts 1 to 4

RudManusachi

RudManusachi

One advantage of using Task over GenServer comes to mind is the fact that Tasks have built in support for Ancestor and Caller Tracking which allows to easily test them with async: true.

Especially for your scenario API call can be easily mocked with Mox:

if you’re running on Elixir 1.8.0 or greater and your concurrency comes from a Task then you don’t need to add explicit allowances. Instead $callers is used to determine the process that actually defined the expectations.

source: Mox # Explicit allowances

And similarly Ecto Sandbox uses DBConnection that does callers lookup which again allows to run tests asynchronously.

To learn more in deep about the subject I highly recommend to take a look at the video series The Process by @ityonemo and particularly Tests with Mox and Ecto

ityonemo

ityonemo

I’m not convinced that using a task just because it gives you :$callers is the right move. Something that responds to a fixed-time recurring event is a much better fit for a GenServer responding to :timer.send_interval. part of the point of the videos is to show you how to make it so that if you do something like that sort of GenServer, how to get it to respect Mox or Ecto.checkouts :wink: hint: pass caller information in start_link

benwilson512

benwilson512

Author of Craft GraphQL APIs in Elixir with Absinthe

GenServers also have ancestors so I’m not really sure that this is a relevant bit here.

@mekusigjinn it is much more idiomatic to use a GenServer for polling than a task. A GenServer with send_after will also let you inspect it with :sys.get_state and so on because it isn’t blocking while waiting.

mekusigjinn

mekusigjinn OP

Wow that’s some deep level GenServer operations there. I’ll be sure to look at the video series. Thanks!

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New

Other Trending Topics Top

mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews