ketupia
Marlus presented techniques for optimizing liveview. One of his last points was to batch socket updates (timestamp 25:55).
All I’ve imagined so far is updating a structure in the socket that the view doesn’t use and then copying it to the active socket assigns peridoically. How would you approach this?
Trending in Questions
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
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
Hi everyone,
I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding.
I sta...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
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
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
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
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
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
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex











Showing Posts 1 to 6- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
rhcarvalho
Hi! That presentation is really great, right? I don’t have access to the code, but from what I could see (watching again the relevant part) is:
Batchermodule that implements anon_mounthookhandle_event(could also do the same forhandle_info…)on_mount/1andattach_hook/4for how to accomplish the above:handle_eventlifecycle hook callsmodule.handle_batchwith a similar signature to the original either after a given number of items are collected or a timeoutBatcheris a behaviour that declares thehandle_batchaboveI could imagine implementing the above with no external dependency. Maybe something like GenStage — gen_stage v1.3.2 or Broadway — Broadway v1.3.0 can be useful for more complex cases.
A question might be where to store the current batch items. I think there are a few options:
Socket.privateusingput_private/3, so that changes are not trackedGenServerrhcarvalho
Here’s a single file demo implementation:
(also available as a GitHub Gist: Phoenix LiveView event batching · GitHub)
ketupia
First off - very nice and clean!! Thank you!
Your solution exposed me to a couple of facilities I hadn’t encountered before like LiveView.attach_hook and LiveView.put_private.
hlx
This might help you in the future
https://github.com/phoenix-playground/phoenix_playground
ketupia
Well that’s fun and - bonus - now I know you can run Phoenix LiveView from Live Book!
ketupia
I’ve reworked my version a bit. Thanks again to rhcarvalho. I couldn’t have done this without your version.
I realized I needed
Since the msg param of handle_info can be data of any shape, I added a callback to know when to throttle. The callback can use pattern matching or any other means.
Actually the first message and any other message when a batch hasn’t been processed since the timeout.
Let’s say the timeout is 500ms and 1000ms goes by since the last batch. The next message should be released immediately.
Here’s my updated version.