valyala/fasthttp

Feature request : update and show all examples for doing zero allocation when using fasthttp. 100% zero alloc for each req / resp.

Open

#1764 opened on Apr 22, 2024

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Go (21,741 stars) (1,755 forks)batch import
help wanted

Description

Would it be more accurate to reconsider the representation of "doing nothing" when displaying 0 alloc/op? Could we perhaps offer a benchmark showcasing alloc/op for a basic "hello world" scenario?

I was taken aback by the alloc/op for the "hello world" scenario. Is there a chance I missed something in my approach? Could we illustrate a scenario with significantly reduced alloc/op?

For instance, could we explore employing the HTTP parser for header parsing?

Alternatively, could we examine a scenario where we could utilize the package from uptrace.dev, which boasts zero alloc for parsing HTTP headers, among other features?

P.S.: I'm expressing this as an avid supporter of fasthttp and eagerly anticipating enhancements, as i am adopting this package across various applications.

is there a hello world http parsing example with lesser garbage generated ?

Contributor guide

Tech stack
go
Domain
performance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
needs maintainer response
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Go knowledgefasthttp basicsbenchmarking concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate current fasthttp benchmark examples in the examples or benchmarks directory. Identify where allocations occur in a simple hello world handler. Consider integrating zero allocation header parsing from uptrace.dev or similar. Provide updated benchmarks comparing before and after. Reference existing fasthttp zero alloc documentation.