valyala/fasthttp

Fast HTTP package for Go. Tuned for high performance. Zero memory allocations in hot paths. Up to 10x faster than net/http

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 56 minutes ago
Added to GitGenius on September 2nd, 2026
Created on October 18th, 2015
Open Issues & Pull Requests: 86 (+0)
GitHub issues: Enabled
Number of forks: 1,858
Total Stargazers: 23,467 (+0)
Total Subscribers: 383 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 30.1 hours
Mean response time: 9.1 days
90th percentile: 9.9 days
Tracked items: 248

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "bug" is answered fastest, typically in about 23 hours, while "beginner friendly" waits about 2 weeks. Only 13% of issues opened in the past year have been closed. Three people close 88% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 65
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 1,338 days
Stale 30+ days: 16
Stale 90+ days: 16

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 1

Top labels

  • help wanted (47)
  • bug (29)
  • wontfix (22)
  • beginner friendly (13)

Detailed Description

fasthttp is a high-performance HTTP package for Go designed as an alternative to the standard library's net/http.

The project addresses the performance limitations of Go's standard HTTP implementation by eliminating memory allocations in hot code paths. It achieves this through careful optimization of request and response handling, buffer reuse, and connection management. The approach focuses on reducing garbage collection pressure and improving throughput for latency-sensitive applications.

Developers should consider fasthttp for projects where HTTP performance is critical, particularly high-throughput servers handling many concurrent connections. It suits scenarios where the overhead of the standard library becomes a bottleneck. However, adoption requires awareness that fasthttp does not implement the standard http.Handler interface, meaning existing code built around net/http cannot be directly ported. Projects already using net/http middleware and frameworks will face integration challenges, whereas new services designed around fasthttp's API can take full advantage of its performance characteristics.

The project shows consistent maintenance with regular updates addressing bug fixes and compatibility improvements. Development activity demonstrates responsiveness to reported issues and a focus on preserving the core optimization principles that define the tool's purpose.