Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't enable WebSocket compression by default #912

Merged
merged 3 commits into from
Jun 18, 2024
Merged

Conversation

neilalexander
Copy link
Member

Currently there are some problems where the flate writer might take up more allocations than expected when there are lots of WebSocket clients.

Signed-off-by: Neil Twigg neil@nats.io

Currently there are some problems where the flate writer might take
up more allocations than expected when there are lots of WebSocket
clients.

Signed-off-by: Neil Twigg <neil@nats.io>
@caleblloyd
Copy link
Contributor

My original thought was that enabling compression by default was good for most common use cases, since Cloud Provider bandwidth is so expensive.

But if the desire is to optimize for high performance scenarios on fast network connections, I digress.

The tests that assert compression is on in the chart’s test sub directory need to be changed from true to false

Caleb Lloyd added 2 commits June 18, 2024 10:36
Signed-off-by: Caleb Lloyd <caleb@synadia.com>
Signed-off-by: Caleb Lloyd <caleb@synadia.com>
@caleblloyd caleblloyd merged commit 1c224be into main Jun 18, 2024
5 checks passed
@caleblloyd caleblloyd deleted the ws-compression branch June 18, 2024 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants