Optimize compression protocol
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 73
- Forks
- 41
- Avg merge
- 21h 3m
- Merged PRs (30d)
- 21
Description
Development Task
Currently, compression protocol is too slow to be practical. 75% of the time is cost by compression and 25% by uncompression. We can optimize this process: if the data can be sent to the client directly, TiProxy doesn't need to compress it again.
This is in lower priority because the compression protocol is barely used in MySQL.
Contributor guide
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
Start by locating TiProxy's compression protocol implementation and measuring the compression and uncompression costs described in the issue. Determine when data can be sent directly to the client without recompression; done means the protocol avoids redundant compression and is measurably faster.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100