dan-cooke
Hi all,
I’m just learning elixir for fun , and I would love to understand a little bit more about the memory allocations that are made during the following code snippet taken from the Mix OTP tutorial:
defp loop_acceptor(socket) do
{:ok, client} = :gen_tcp.accept(socket)
{:ok, pid} = Task.Supervisor.start_child(KVServer.TaskSupervisor, fn -> serve(client) end)
:ok = :gen_tcp.controlling_process(client, pid)
loop_acceptor(socket)
end
Heres what I am thinking so far:
loop_acceptorfunction is called andsocketis placed onto the stack for this function call:gen_tcp.accept(socket)is called which creates a socket resource calledclient, this is currently owned by the process that calledloop_acceptorTask.Supervisor.start_childis called, the anon function creates a closure which captures theservefunction and theclient.
Thats where I get stuck.
- Does this closure which runs in a new process result in the variables it captures being “copied” into the new process heap/stack?
- If so.. how is it possible to “copy” a resource like a socket without creating multiple OS sockets for the same connection?
- As the serve function belongs to the surrounding
KVServermodule does this mean that the supervised task gets a copy of the KVServer module too?
If anyone has any good documentation to learn more about BEAM memory, or perhaps some tips on how I can debug these allocations myself.
I’m very green with BEAM
Any help is greatly appreciated, thanks!
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
I’m aware of 2 such projects, are there others?
git: GitHub - team-alembic/realworld: A fullstack Phoenix LiveView application with back...
New
Hi everyone.
My team and I have been working on a fairly modest app based around video streaming and chat, but we’ve landed a customer t...
New
I really like the adapter patterns that ecto, nebulex, waffle, etc. use and would love find something similar for a key management servic...
New
Hello folks!
So at work, we are seeing some situations where we have to define some “fixed” strings that are used across the codebase in...
New
How Can I Optimise Compile Time Dependencies
I have been building an elixir application for about 2 years now. Many modules and files ha...
New
Hi,
we run different LLM models across a cluster, with each node loading a configurable subset. Model-specific queues let nodes consume ...
New
Other Trending Topics
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
New
I love Elixir. It’s one of 2 programming languages I’ve ever fallen in love with.
But I don’t use it anymore.
Serverless was the promis...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #hex










Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
derek-zhou
The authoritative source of BEAM internal is the Beam book:
It really depends on how deep you want to go. From the 10,000 foot above, you can consider all values are allocated on the per-process heap and are immutable. So there will not be cyclic references, GC is straight forward, and closure is easy to implement.
Of cause there are exceptions, but the native code hide the ugly parts and maintain the happy illusion.
al2o3cr
#1: yes, the closure captures its environment. Rebinding
clientafter the call toTask.Supervisor.start_childwon’t change the value the child process sees.#2: the thing that’s returned from
:gen_tcp.acceptis usually a “port”; short short version it’s a way to name the thing that’s actually holding the OS socket. Callingcontrolling_processtells the port that it should send messages etc to the newly-started task instead of the process that originally called:gen_tcp.accept.#3: there’s no state attached to the module
KVServer, so asking whether there’s a second “copy” of it isn’t particularly meaningful. There’s some very tricky corner-cases around hot-code reloading that make callingserve(client)different from callingKVServer.serve(client)(even from inside a function defined inKVServer!) but most people will never encounter them.