PJUllrich

PJUllrich

Author of Building Table Views with Phoenix LiveView

I’m currently playing around with GenServers and for a totally unrealistic, but still interesting problem, I wondered whether there is a faster way of spawing 40.000+ processes than this:

pids = for id <- 1..40_000 do
  {:ok, pid} = GenServer.start_link(MyGenServerModule, id: id)
  pid
end

Since this for-loop runs synchronously, it takes around 10 to 12 seconds on my macBook to spawn all 40k processes. I wondered, whether this could somehow be achieved asynchronously?

Showing Posts 1 to 10

hauleth

hauleth

You want just to spawn them or get their PIDs as well? Should these processes be inside supervision tree?

PJUllrich

PJUllrich OP

Author of Building Table Views with Phoenix LiveView

I need their I PIDs to send messages to them. A supervisor is not needed. I want to spawn them inside a LiveView process and have them linked to that LV process.

princemaple

princemaple

1..40_000 |> Task.async_stream(fn _ → YOUR_CODE end) |> Enum.to_list

Not sure what evil thing you are trying to do… I won’t ask :thinking:

PJUllrich

PJUllrich OP

Author of Building Table Views with Phoenix LiveView

Thank you! That indeed decreased the execution time from ~12s to ~1.2s, but unfortunately, I believe the processes weren’t linked to the original process correctly. Maybe because the GenServer.start_link/2 was called inside the Task.async_stream? Will those processes then correctly be linked to the “parent process” in which I used to call the GenServer.start_link/2 function originally?

PS: I’m currently playing around with simulating the Game of Life with 50.000 erlang processes. Because, why not? :smiley:

10
Post #4
princemaple

princemaple

Hi, That’s pretty cool.

To link the process to your main process, you can do this:
1..40_000 |> Task.async_stream(fn _ -> YOUR_CODE end) |> Enum.map(fn {:ok, pid} -> Process.link(pid) end)

PJUllrich

PJUllrich OP

Author of Building Table Views with Phoenix LiveView

Unfortunately, that took even longer than the sequential loop. Sequential was 12s and this version was something between 60 and 85s :frowning_face: I decided on using the sequential version now, but thank you anyway :heart:

Sebb

Sebb

how about starting the processes in some DynamicSupervisors?

princemaple

princemaple

That’s weird. On my machine they hardly differ. :thinking:

qhwa

qhwa

Spawning processes, even GenServer processes, is fast in Elixir. I just wrote this script based on your code to test:

defmodule MyGenServerModule do
  use GenServer

  @impl true
  def init(state) do
    {:ok, state}
  end

  @impl true
  def handle_call(:ping, _from, state) do
    {:reply, {:pong, state[:id]}, state}
  end
end

{t, pids} =
  :timer.tc(fn ->
    for id <- 1..40_000 do
      {:ok, pid} = GenServer.start_link(MyGenServerModule, id: id)
      pid
    end
  end)

IO.inspect("started #{length(pids)} processes in #{div(t, 1000)} ms")

Enum.random(pids) |> GenServer.call(:ping) |> IO.inspect()

The output I got:

"started 40000 processes in 521 ms"
{:pong, 2861}

So maybe you’re doing too much work in the init/1 callback? If true, you can move the hard work into a handle_info/2 callback, by sending a message to self in the init callback. For example:

def init(state) do
  send(self(), :start)
  {:ok, state}
end

def handle_info(:start, state) do
  # start living
end

Edit: :conitune tuple mentioned by @lud is better.

lud

lud

I played with that problem and had 4 processes spawn 10 processes spawn 10 processes spawn 10 processes, etc, to spawn 40K processes.

It is fast, but not that much faster than spawning them sequentially. And if you do that then I don’t know how you could supervise those processes.

For better synchronization I would pick a timestamp 3 seconds in the future, spawn all processes sequentially and have them wait that precise timestamp to start the logic in sync.

Here is my test code:

defmodule Serv do
  use GenServer

  def start_nolink(id, parent) do
    GenServer.start(__MODULE__, {id, parent})
  end

  def init({id, parent}) do
    Process.link(parent)
    send(parent, {:started, id})
    {:ok, id}
  end
end

defmodule Spawner do
  def rec_spawn(parent, scheme) do
    rec_spawn(parent, scheme, 0)
  end

  defp rec_spawn(parent, [], sum) do
    Serv.start_nolink(sum, parent)
  end

  defp rec_spawn(parent, [range | ranges], sum) do
    sum = sum * 10
    starter = fn -> Enum.map(range, &rec_spawn(parent, ranges, sum + &1)) end
    spawn(starter)
  end
end

defmodule Control do
  def check_started(max) do
    _check_started(max + 1)
  end

  defp _check_started(max) do
    case Process.info(self(), :message_queue_len) do
      {:message_queue_len, ^max} ->
        IO.puts("all started OK")

        flush_all()

      {:message_queue_len, n} when n < max ->
        IO.puts("started #{n}/#{max}")
        Process.sleep(100)
        _check_started(max)
    end
  end

  defp flush_all() do
    receive do
      {:started, _} ->
        flush_all()
    after
      0 -> :ok
    end
  end

  def sum_ranges(ranges) do
    {sum, _} =
      List.foldr(ranges, {0, 1}, fn range, {sum, size} ->
        {sum + Enum.max(range) * size, size * 10}
      end)

    sum
  end
end

ranges = [0..3, 0..9, 0..9, 0..9, 0..9]

parent = self()
Spawner.rec_spawn(parent, ranges)

ranges
|> Control.sum_ranges()
|> Control.check_started()

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
kszambelanczyk
Hello! Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app. I creat...
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
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
ryanwinchester
apply_graft/2 doesn’t rewrite an add_many sub-workflow’s deps on an add step. Grafted jobs cancel with “upstream job was deleted” Version...
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
garrison
Hobbes is a low-level distributed database for the Elixir programming language. Hobbes provides a simple, safe, and scalable storage lay...
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
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
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge &amp; Solve. They are GUI (Emerge) and State management (S...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews