Jump to content

when to use websocket compression/perMessageDeflate?


 Share

Recommended Posts

I have been unable to find good information as to the usefulness/practicality of the perMessageDeflate option/module.

Suppose I have messages that are 1000 bites (the length of the text string), being sent out 10 times per second (every 100 ms), is compression worth it there?

I have heard that perMessageDeflate can be a monster on CPU usage. I imagine it is not cost-effective if your messages are really small and infrequent.

Anyway, does anyone have any idea what the threshold is? At what point in packet size and frequency (i.e. bandwidth) is using perMessageDeflate a smart idea?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...