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 建立於 2024年4月22日

在 GitHub 查看
 (3 留言) (0 反應) (0 負責人)Go (21,741 star) (1,755 fork)batch import
help wanted

描述

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 ?

貢獻者指南

技術棧
go
領域
performance
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
needs maintainer response
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
needs investigation
前置要求
Go knowledgefasthttp basicsbenchmarking concepts
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
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.