clemensm
Hi everyone
I’m currently developing an app using Phoenix LiveView, and we’ve got one component (search) where we’ve got to push rather large chanes over the wire (html up to ca. 700kB).
When I was checking on how we could speed the transfer of this up I realized that the websocket does not seem to use compression for the diffs, is there a way to turn this on? I’ve looked around on the web, and setting:
x_web/config/prod.exs
config x_web, XWeb.Endpoint,
http: [compress: true ...]
does not seem to help. This will compress the http requests, but the diffs over the Websocket seem to be still uncompressed.
I’ve tested this using Firefox and Chrome, and have the same result in both environments (using Phoenix 1.5, LiveView 0.14.1, cowboy 2.8.0)
Thanks for the help
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
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
Other Trending Topics
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
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
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
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security










Showing Posts 1 to 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
clemensm
Ok, found it after digging through the documentation in depth. Just enable the
compress=truein the socket, like for any other channel, the setting is then passed along to cowboy.I.e. in your
endpoint.ex, do this:And here ist the documentation for it.
sfusato
Have you measured the difference before and after in size and maybe also processing time?
clemensm
Sadly I’ve found no way to measure the size, all browsers seem to display only the size of the uncompressed message.
However I was able to “somewhat” measure the reduced time. Messages took roughly 450 ms to deliver before (I knew that ~150ms where spend on the server on the actual logic), and times are now down to ~200ms. So seems to be working as expected.
drathier
Old post, but phoenix dashboard total input / total output clearly shows that compression works
Sending 1MB of test data roundtrip results in just over a 1MB increase in those numbers with compression off, and about 110kB with compression on. Browsers still completely hide whether or not compression was used.
ndrean
[See correction below]
I send a 1.1MB payload - a JSON string - from the server via a
pushEventalong the liveSocket.The network/socket shows that I send indeed 1.1MB.
To inspect the “real” size, I inspect the loopback with
Wireshark.Without
compress: true, I see 70 TCP packets × ~16 KB = ~1.1 MB. No compression is applied.Digging further, I should see RSV1 bit should be set 1, but Wireshark displays nothing.This confirms that Bandit does only negotiate but does not apply any compression at all on the framesSo how do you see your results above?Edit.
When you do set “compress”, I see that 18 packets have been sent for a length of 276kB. This means that Bandit compression correctly.