clockworklabs / clockworklabs/SpacetimeDB
PERFORMANCE FIX: Zstd streaming compression for websocket
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
This seems like a massive, HUGE, low-hanging fruit performance improvement that you could make for Maincloud and STDB. Enable Zstd streaming compression as an option for websocket messages. Based on the Discord case study (and various other online studies), the results seem absolutely impressive.
Case study: https://discord.com/blog/how-discord-reduced-websocket-traffic-by-40-percent
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating websocket message handling and its compression configuration, then review the linked Discord case study; done should mean Zstd streaming compression is available as an option for websocket messages with coverage for the new behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 43/100