Improve HTTP response buffering
Open
theme/internal-cleanup
type/enhancement
- Dominant language
- Go
- Stars
- 30.1k
- Forks
- 4.6k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 39
Description
During some operations with large JSON responses we see memory usage on the order of 3X the actual data size. We should chunk/stream big responses to avoid so many intermediate, full-sized copies.
Contributor guide
Research direction
No file or test is named. Start by tracing Consul’s HTTP response handling and measuring large JSON responses to identify where full-sized copies are created. Done means large responses are chunked or streamed and memory usage no longer grows to several times the response size.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100