clemensm

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

Showing Posts 1 to 5

clemensm

clemensm OP

Ok, found it after digging through the documentation in depth. Just enable the compress=true in the socket, like for any other channel, the setting is then passed along to cowboy.

I.e. in your endpoint.ex, do this:

socket "/live", Phoenix.LiveView.Socket, websocket: [compress: compress]

And here ist the documentation for it.

sfusato

sfusato

Have you measured the difference before and after in size and maybe also processing time?

clemensm

clemensm OP

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

drathier

Old post, but phoenix dashboard total input / total output clearly shows that compression works :slight_smile: 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.

  socket "/my-socket", MyWeb.MySocket,
   longpoll: true,
   websocket: [compress: true]
ndrean

ndrean

[See correction below]

I send a 1.1MB payload - a JSON string - from the server via a pushEvent along 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 frames
So how do you see your results above?

Edit. :double_exclamation_mark: When you do set “compress”, I see that 18 packets have been sent for a length of 276kB. This means that Bandit compression correctly.

— All posts loaded —

Where Next? Top

Trending in Questions Top

Blokh
Hey guys, I’ve got a huge CSV ( around 10 GB ) that needs to be processed hourly Do you guys have any suggestions what is the best prac...
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
matt-savvy
Anyone here using Honeybadger? My Honeybadger account is being overwhelmed with noise from some bots. Seeing a lot of Bandit.HTTPError...
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
garrison
Hobbes is a low-level distributed database for the Elixir programming language. Hobbes provides a simple, safe, and scalable storage lay...
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
mcass19
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve. They are GUI (Emerge) and State management (S...
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