Add benchmarks for decoders
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 504
- Forks
- 263
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 5
Description
https://github.com/ozontech/file.d/tree/master/decoder
We have several of them, it would be useful to have benchmarks to see if we degrade on any of them
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 reading the decoders in the repository's decoder directory and identify the existing decoder implementations and test conventions. Add benchmarks covering the several decoders so their performance can be compared over time. Done means the decoder benchmarks are present and can expose performance degradation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- performance, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100