You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+18-14Lines changed: 18 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,12 @@
4
4
5
5
Fast HTTP implementation for Go.
6
6
7
+
# fasthttp might not be for you!
8
+
fasthttp was design for some high performance edge cases. **Unless** your server/client needs to handle **thousands of small to medium requests per seconds** and needs a consistent low millisecond response time fasthttp might not be for you. **For most cases `net/http` is much better** as it's easier to use and can handle more cases. For most cases you won't even notice the performance difference.
9
+
10
+
11
+
## General info and links
12
+
7
13
Currently fasthttp is successfully used by [VertaMedia](https://vertamedia.com/)
8
14
in a production serving up to 200K rps from more than 1.5M concurrent keep-alive
9
15
connections per physical server.
@@ -34,7 +40,7 @@ connections per physical server.
34
40
35
41
[FAQ](#faq)
36
42
37
-
# HTTP server performance comparison with [net/http](https://golang.org/pkg/net/http/)
43
+
##HTTP server performance comparison with [net/http](https://golang.org/pkg/net/http/)
38
44
39
45
In short, fasthttp server is up to 10 times faster than net/http.
*[Gearbox](https://github.com/gogearbox/gearbox) - :gear: gearbox is a web framework written in Go with a focus on high performance and memory optimization
506
512
507
513
508
-
# FAQ
514
+
##FAQ
509
515
510
516
**Why creating yet another http package instead of optimizing net/http?*
0 commit comments