elastic / elastic/go-docappender
investigate buffering data before gzipping
Open
- Dominant language
- Go
- Stars
- 11
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Some high cpu usage was observed in the docappender when writing to the gzip writer.
Investigate if we need to buffer data before writing
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the docappender path that writes to the gzip writer and reproduce or profile the high CPU usage described in the issue. Done means determining whether buffering is needed before gzip writes and documenting or implementing the chosen change with evidence that CPU usage is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100