Feature: Move to jx decoder in proxy
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 131
- Forks
- 16
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 11
Description
In attempt to reduce allocations during field indexing, we decided to try jx decoder in proxy, instead of insane-json
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
The issue names the proxy and its current insane-json decoder; start by locating that decoder usage and reviewing how field indexing is handled. Compare the jx decoder integration and measure allocations before and after. Done means the proxy uses jx without breaking indexing behavior and the allocation goal is validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, databases, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100