networknt / networknt/microservices-framework-benchmark
Go FastHttp Avg Latency Wrong?
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 715
- Forks
- 120
- PR merge metrics
- No merged PRs in 30d
Description
Go FastHttp's average latency of 99.98ms in the readme seems wrong. I would think with its throughput and transfer and that it's on top of the list, its average latency would be lower. Maybe it's supposed to be 99.98 nanos? Or it's just a typo?
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 checking the FastHttp average-latency entry in the README and compare its value and unit with the benchmark results in this repository. Done means determining whether 99.98ms is correct or a typo, then updating the README if the documented value is wrong.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- documentation, performance
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100