valyala/fasthttp

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

Open

#1.764 aberto em 22 de abr. de 2024

Ver no GitHub
 (3 comments) (0 reactions) (0 assignees)Go (1.755 forks)batch import
help wanted

Métricas do repositório

Stars
 (21.741 stars)
Métricas de merge de PR
 (Mesclagem média 1d 11h) (34 fundiu PRs em 30d)

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 ?

Guia do colaborador