Fast HTTP package for Go. Tuned for high performance. Zero memory allocations in hot paths. Up to 10x faster than net/http
Latest commit 2ada93a Jan 18, 2017 @valyala Document that the cookie passed to ResponseHeader.SetCookie may be re…
…-used after the function returns
Failed to load latest commit information.
examples typo fix after f340a29 Feb 5, 2016
expvarhandler expvarhandler: properly generate json output when regexp filter is pr… Sep 27, 2016
fasthttpadaptor go vet fix Sep 27, 2016
fasthttputil fasthttputil.PipeConns: add read/write deadline support Sep 26, 2016
reuseport switch reuseport to Sep 13, 2016
stackless stackless: optimization: do not issue zero-length writes to underlyin… Nov 11, 2016
.gitignore Ignore *.fasthttp.gz files Dec 29, 2015
.travis.yml run travis tests on go 1.7 Aug 17, 2016
LICENSE Updated LICENSE Mar 1, 2016 Issue #207: mention lu in more places. Remove echo, since it dropped … Dec 5, 2016
TODO Added PipelineClient for issuing pipelined requests to the server Apr 1, 2016
args.go Added Args.Add() Mar 29, 2016
args_test.go Issue #69: Added RequestHeader.Add and ResponseHeader.Add for adding … Mar 29, 2016
args_timing_test.go Added benchmark for Args.Peek() Nov 14, 2015
bytebuffer.go Deprecate ByteBuffer in favor of bytebufferpool Jun 24, 2016
bytebuffer_example_test.go typo fix Feb 11, 2016
bytebuffer_test.go Exported ByteBuffer Feb 11, 2016
bytebuffer_timing_test.go Added benchmarks for bytes.Buffer vs ByteBuffer comparison Feb 12, 2016
bytesconv.go Properly handle hashes and single dots in URI.Update (see kataras/iri… Jun 7, 2016
bytesconv_32.go Updated test matrix in .travis.yml according to… Dec 1, 2015
bytesconv_32_test.go Updated test matrix in .travis.yml according to… Dec 1, 2015
bytesconv_64.go Updated test matrix in .travis.yml according to… Dec 1, 2015
bytesconv_64_test.go Updated test matrix in .travis.yml according to… Dec 1, 2015
bytesconv_test.go Added AppendHTMLEscape helper function Feb 15, 2016
bytesconv_timing_test.go Added AppendHTMLEscape helper function Feb 15, 2016
client.go client: retry non-idempotent requests if the server closes idle keep-… Nov 28, 2016
client_example_test.go Added an example for HostClient Dec 21, 2015
client_test.go Properly set "https" scheme in RequestCtx.URI() for TLS connections Jan 14, 2017
client_timing_test.go Added support for multiple concurrent connections to server in Pipeli… Jul 16, 2016
compress.go Reduce stack space usage when using response compression Nov 3, 2016
compress_test.go Added AppendGzipBytes and AppendGunzipBytes for simplifying gzipping/… Dec 31, 2015
cookie.go Issue #141: do not urlencode cookies Jul 18, 2016
cookie_test.go Issue #141: do not urlencode cookies Jul 18, 2016
cookie_timing_test.go Added Cookie.ParseBytes to be consistent with Args Nov 5, 2015
doc.go Added ability to filter out non-GET requests Nov 29, 2015
fs.go Revert "Use standard compress packages until klauspost/compress#64 is… Oct 20, 2016
fs_example_test.go Fixed a typo Dec 29, 2015
fs_handler_example_test.go Added an example for FS Dec 29, 2015
fs_test.go Add test for fsSmallFileReader.WriteTo and fix bug (#128) Jul 12, 2016
header.go Document that the cookie passed to ResponseHeader.SetCookie may be re… Jan 18, 2017
header_regression_test.go Issue #28: do not set default Content-Type for empty response Jan 4, 2016
header_test.go Issue #173: improve error messages on headers parsing Nov 10, 2016
header_timing_test.go Issue #57: Server: added ability to disable header names' normalizing Feb 25, 2016
http.go Properly set "https" scheme in RequestCtx.URI() for TLS connections Jan 14, 2017
http_test.go Issue #193: properly handle nil body when calling WriteGzip* and Writ… Oct 31, 2016
lbclient.go LBClient: prevent servers' hammering by randomizing the initial clien… Nov 9, 2016
lbclient_example_test.go Added an example for LBClient Oct 21, 2016
nocopy.go Do not expose noCopy.Lock Mar 4, 2016
peripconn.go scalability improvement: use per-server peripconn pool Mar 30, 2016
peripconn_test.go Added ability to limit the number of concurrent client connections pe… Nov 2, 2015
requestctx_setbodystreamwriter_example_test.go Issue #78: Added an example for RequestCtx.SetBodyStreamWriter Apr 15, 2016
server.go Properly set "https" scheme in RequestCtx.URI() for TLS connections Jan 14, 2017
server_example_test.go Import fasthttp in server examples Dec 21, 2015
server_test.go Properly set "https" scheme in RequestCtx.URI() for TLS connections Jan 14, 2017
server_timing_test.go Benchmark server with 10K concurrent clients instead of 1K clients Dec 2, 2015
ssl-cert-snakeoil.key Added missing snakeoil ssl certificates for client tests Nov 12, 2015
ssl-cert-snakeoil.pem Added missing snakeoil ssl certificates for client tests Nov 12, 2015
status.go add missing http status codes (#140) Jul 18, 2016
stream.go Removed 'recover-from-panic' band-aids. Jul 12, 2016
stream_test.go Simplified PipeConns - now they properly handle the case when reader … Jun 10, 2016
stream_timing_test.go Use fasthttp.PipeConns instead of io.Pipe in StreamReader Jun 10, 2016
strings.go Issue #107 (#108) May 27, 2016
tcpdialer.go Issue #196: avoid returning (nil, nil) from fasthttp.Dial* Oct 29, 2016
timer.go removed memory allocations from tryDial. This should improve performa… May 16, 2016
uri.go Updated tests and documentation for URI.Parse and URI.Update* regardi… Jan 9, 2017
uri_test.go Updated tests and documentation for URI.Parse and URI.Update* regardi… Jan 9, 2017
uri_timing_test.go Hide Request.URI and Request.PostArgs behind accessors, which automat… Nov 15, 2015
uri_unix.go go fmt May 4, 2016
uri_windows.go go fmt May 4, 2016
uri_windows_test.go Issue #86: Fixed leading slash on Windows May 4, 2016
userdata.go Renamed unsafeBytes2Str to b2s Mar 29, 2016
userdata_test.go Call Close on user values stored via RequestCtx.SetUserValue if these… Feb 5, 2016
userdata_timing_test.go Moved ctx.UserValue from standard map to custom userData. This should… Dec 11, 2015
workerpool.go optimization: removed slow defer from worker pool handler and hijack … Jul 18, 2016
workerpool_test.go Removed 'recover-from-panic' band-aids. Jul 12, 2016

Build Status GoDoc Go Report


Fast HTTP implementation for Go.

Currently fasthttp is successfully used by VertaMedia in a production serving up to 200K rps from more than 1.5M concurrent keep-alive connections per physical server.

TechEmpower Benchmark round 12 results

Server Benchmarks

Client Benchmarks



Examples from docs

Code examples

Switching from net/http to fasthttp

Fasthttp best practices

Tricks with byte buffers

Related projects


HTTP server performance comparison with net/http

In short, fasthttp server is up to 10 times faster than net/http. Below are benchmark results.


net/http server:

$ GOMAXPROCS=1 go test -bench=NetHTTPServerGet -benchmem -benchtime=10s
BenchmarkNetHTTPServerGet1ReqPerConn                     1000000         12052 ns/op        2297 B/op         29 allocs/op
BenchmarkNetHTTPServerGet2ReqPerConn                     1000000         12278 ns/op        2327 B/op         24 allocs/op
BenchmarkNetHTTPServerGet10ReqPerConn                    2000000          8903 ns/op        2112 B/op         19 allocs/op
BenchmarkNetHTTPServerGet10KReqPerConn                   2000000          8451 ns/op        2058 B/op         18 allocs/op
BenchmarkNetHTTPServerGet1ReqPerConn10KClients            500000         26733 ns/op        3229 B/op         29 allocs/op
BenchmarkNetHTTPServerGet2ReqPerConn10KClients           1000000         23351 ns/op        3211 B/op         24 allocs/op
BenchmarkNetHTTPServerGet10ReqPerConn10KClients          1000000         13390 ns/op        2483 B/op         19 allocs/op
BenchmarkNetHTTPServerGet100ReqPerConn10KClients         1000000         13484 ns/op        2171 B/op         18 allocs/op

fasthttp server:

$ GOMAXPROCS=1 go test -bench=kServerGet -benchmem -benchtime=10s
BenchmarkServerGet1ReqPerConn                           10000000          1559 ns/op           0 B/op          0 allocs/op
BenchmarkServerGet2ReqPerConn                           10000000          1248 ns/op           0 B/op          0 allocs/op
BenchmarkServerGet10ReqPerConn                          20000000           797 ns/op           0 B/op          0 allocs/op
BenchmarkServerGet10KReqPerConn                         20000000           716 ns/op           0 B/op          0 allocs/op
BenchmarkServerGet1ReqPerConn10KClients                 10000000          1974 ns/op           0 B/op          0 allocs/op
BenchmarkServerGet2ReqPerConn10KClients                 10000000          1352 ns/op           0 B/op          0 allocs/op
BenchmarkServerGet10ReqPerConn10KClients                20000000           789 ns/op           2 B/op          0 allocs/op
BenchmarkServerGet100ReqPerConn10KClients               20000000           604 ns/op           0 B/op          0 allocs/op


net/http server:

$ GOMAXPROCS=4 go test -bench=NetHTTPServerGet -benchmem -benchtime=10s
BenchmarkNetHTTPServerGet1ReqPerConn-4                       3000000          4529 ns/op        2389 B/op         29 allocs/op
BenchmarkNetHTTPServerGet2ReqPerConn-4                       5000000          3896 ns/op        2418 B/op         24 allocs/op
BenchmarkNetHTTPServerGet10ReqPerConn-4                      5000000          3145 ns/op        2160 B/op         19 allocs/op
BenchmarkNetHTTPServerGet10KReqPerConn-4                     5000000          3054 ns/op        2065 B/op         18 allocs/op
BenchmarkNetHTTPServerGet1ReqPerConn10KClients-4             1000000         10321 ns/op        3710 B/op         30 allocs/op
BenchmarkNetHTTPServerGet2ReqPerConn10KClients-4             2000000          7556 ns/op        3296 B/op         24 allocs/op
BenchmarkNetHTTPServerGet10ReqPerConn10KClients-4            5000000          3905 ns/op        2349 B/op         19 allocs/op
BenchmarkNetHTTPServerGet100ReqPerConn10KClients-4           5000000          3435 ns/op        2130 B/op         18 allocs/op

fasthttp server:

$ GOMAXPROCS=4 go test -bench=kServerGet -benchmem -benchtime=10s
BenchmarkServerGet1ReqPerConn-4                             10000000          1141 ns/op           0 B/op          0 allocs/op
BenchmarkServerGet2ReqPerConn-4                             20000000           707 ns/op           0 B/op          0 allocs/op
BenchmarkServerGet10ReqPerConn-4                            30000000           341 ns/op           0 B/op          0 allocs/op
BenchmarkServerGet10KReqPerConn-4                           50000000           310 ns/op           0 B/op          0 allocs/op
BenchmarkServerGet1ReqPerConn10KClients-4                   10000000          1119 ns/op           0 B/op          0 allocs/op
BenchmarkServerGet2ReqPerConn10KClients-4                   20000000           644 ns/op           0 B/op          0 allocs/op
BenchmarkServerGet10ReqPerConn10KClients-4                  30000000           346 ns/op           0 B/op          0 allocs/op
BenchmarkServerGet100ReqPerConn10KClients-4                 50000000           282 ns/op           0 B/op          0 allocs/op

HTTP client comparison with net/http

In short, fasthttp client is up to 10 times faster than net/http. Below are benchmark results.


net/http client:

$ GOMAXPROCS=1 go test -bench='HTTPClient(Do|GetEndToEnd)' -benchmem -benchtime=10s
BenchmarkNetHTTPClientDoFastServer                       1000000         12567 ns/op        2616 B/op         35 allocs/op
BenchmarkNetHTTPClientGetEndToEnd1TCP                     200000         67030 ns/op        5028 B/op         56 allocs/op
BenchmarkNetHTTPClientGetEndToEnd10TCP                    300000         51098 ns/op        5031 B/op         56 allocs/op
BenchmarkNetHTTPClientGetEndToEnd100TCP                   300000         45096 ns/op        5026 B/op         55 allocs/op
BenchmarkNetHTTPClientGetEndToEnd1Inmemory                500000         24779 ns/op        5035 B/op         57 allocs/op
BenchmarkNetHTTPClientGetEndToEnd10Inmemory              1000000         26425 ns/op        5035 B/op         57 allocs/op
BenchmarkNetHTTPClientGetEndToEnd100Inmemory              500000         28515 ns/op        5045 B/op         57 allocs/op
BenchmarkNetHTTPClientGetEndToEnd1000Inmemory             500000         39511 ns/op        5096 B/op         56 allocs/op

fasthttp client:

$ GOMAXPROCS=1 go test -bench='kClient(Do|GetEndToEnd)' -benchmem -benchtime=10s
BenchmarkClientDoFastServer                             20000000           865 ns/op           0 B/op          0 allocs/op
BenchmarkClientGetEndToEnd1TCP                           1000000         18711 ns/op           0 B/op          0 allocs/op
BenchmarkClientGetEndToEnd10TCP                          1000000         14664 ns/op           0 B/op          0 allocs/op
BenchmarkClientGetEndToEnd100TCP                         1000000         14043 ns/op           1 B/op          0 allocs/op
BenchmarkClientGetEndToEnd1Inmemory                      5000000          3965 ns/op           0 B/op          0 allocs/op
BenchmarkClientGetEndToEnd10Inmemory                     3000000          4060 ns/op           0 B/op          0 allocs/op
BenchmarkClientGetEndToEnd100Inmemory                    5000000          3396 ns/op           0 B/op          0 allocs/op
BenchmarkClientGetEndToEnd1000Inmemory                   5000000          3306 ns/op           2 B/op          0 allocs/op


net/http client:

$ GOMAXPROCS=4 go test -bench='HTTPClient(Do|GetEndToEnd)' -benchmem -benchtime=10s
BenchmarkNetHTTPClientDoFastServer-4                         2000000          8774 ns/op        2619 B/op         35 allocs/op
BenchmarkNetHTTPClientGetEndToEnd1TCP-4                       500000         22951 ns/op        5047 B/op         56 allocs/op
BenchmarkNetHTTPClientGetEndToEnd10TCP-4                     1000000         19182 ns/op        5037 B/op         55 allocs/op
BenchmarkNetHTTPClientGetEndToEnd100TCP-4                    1000000         16535 ns/op        5031 B/op         55 allocs/op
BenchmarkNetHTTPClientGetEndToEnd1Inmemory-4                 1000000         14495 ns/op        5038 B/op         56 allocs/op
BenchmarkNetHTTPClientGetEndToEnd10Inmemory-4                1000000         10237 ns/op        5034 B/op         56 allocs/op
BenchmarkNetHTTPClientGetEndToEnd100Inmemory-4               1000000         10125 ns/op        5045 B/op         56 allocs/op
BenchmarkNetHTTPClientGetEndToEnd1000Inmemory-4              1000000         11132 ns/op        5136 B/op         56 allocs/op

fasthttp client:

$ GOMAXPROCS=4 go test -bench='kClient(Do|GetEndToEnd)' -benchmem -benchtime=10s
BenchmarkClientDoFastServer-4                               50000000           397 ns/op           0 B/op          0 allocs/op
BenchmarkClientGetEndToEnd1TCP-4                             2000000          7388 ns/op           0 B/op          0 allocs/op
BenchmarkClientGetEndToEnd10TCP-4                            2000000          6689 ns/op           0 B/op          0 allocs/op
BenchmarkClientGetEndToEnd100TCP-4                           3000000          4927 ns/op           1 B/op          0 allocs/op
BenchmarkClientGetEndToEnd1Inmemory-4                       10000000          1604 ns/op           0 B/op          0 allocs/op
BenchmarkClientGetEndToEnd10Inmemory-4                      10000000          1458 ns/op           0 B/op          0 allocs/op
BenchmarkClientGetEndToEnd100Inmemory-4                     10000000          1329 ns/op           0 B/op          0 allocs/op
BenchmarkClientGetEndToEnd1000Inmemory-4                    10000000          1316 ns/op           5 B/op          0 allocs/op


go get -u

Switching from net/http to fasthttp

Unfortunately, fasthttp doesn't provide API identical to net/http. See the FAQ for details. There is net/http -> fasthttp handler converter, but it is better to write fasthttp request handlers by hand in order to use all of the fasthttp advantages (especially high performance :) ).

Important points:

  • Fasthttp works with RequestHandler functions instead of objects implementing Handler interface. Fortunately, it is easy to pass bound struct methods to fasthttp:

    type MyHandler struct {
      foobar string
    // request handler in net/http style, i.e. method bound to MyHandler struct.
    func (h *MyHandler) HandleFastHTTP(ctx *fasthttp.RequestCtx) {
      // notice that we may access MyHandler properties here - see h.foobar.
      fmt.Fprintf(ctx, "Hello, world! Requested path is %q. Foobar is %q",
          ctx.Path(), h.foobar)
    // request handler in fasthttp style, i.e. just plain function.
    func fastHTTPHandler(ctx *fasthttp.RequestCtx) {
      fmt.Fprintf(ctx, "Hi there! RequestURI is %q", ctx.RequestURI())
    // pass bound struct method to fasthttp
    myHandler := &MyHandler{
      foobar: "foobar",
    fasthttp.ListenAndServe(":8080", myHandler.HandleFastHTTP)
    // pass plain function to fasthttp
    fasthttp.ListenAndServe(":8081", fastHTTPHandler)
  • The RequestHandler accepts only one argument - RequestCtx. It contains all the functionality required for http request processing and response writing. Below is an example of a simple request handler conversion from net/http to fasthttp.

    // net/http request handler
    requestHandler := func(w http.ResponseWriter, r *http.Request) {
      switch r.URL.Path {
      case "/foo":
          fooHandler(w, r)
      case "/bar":
          barHandler(w, r)
          http.Error(w, "Unsupported path", http.StatusNotFound)
    // the corresponding fasthttp request handler
    requestHandler := func(ctx *fasthttp.RequestCtx) {
      switch string(ctx.Path()) {
      case "/foo":
      case "/bar":
          ctx.Error("Unsupported path", fasthttp.StatusNotFound)
  • Fasthttp allows setting response headers and writing response body in an arbitrary order. There is no 'headers first, then body' restriction like in net/http. The following code is valid for fasthttp:

    requestHandler := func(ctx *fasthttp.RequestCtx) {
      // set some headers and status code first
      // then write the first part of body
      fmt.Fprintf(ctx, "this is the first part of body\n")
      // then set more headers
      ctx.Response.Header.Set("Foo-Bar", "baz")
      // then write more body
      fmt.Fprintf(ctx, "this is the second part of body\n")
      // then override already written body
      ctx.SetBody([]byte("this is completely new body contents"))
      // then update status code
      // basically, anything may be updated many times before
      // returning from RequestHandler.
      // Unlike net/http fasthttp doesn't put response to the wire until
      // returning from RequestHandler.
  • Fasthttp doesn't provide ServeMux, but there are more powerful third-party routers and web frameworks with fasthttp support:

    Net/http code with simple ServeMux is trivially converted to fasthttp code:

    // net/http code
    m := &http.ServeMux{}
    m.HandleFunc("/foo", fooHandlerFunc)
    m.HandleFunc("/bar", barHandlerFunc)
    m.Handle("/baz", bazHandler)
    http.ListenAndServe(":80", m)
    // the corresponding fasthttp code
    m := func(ctx *fasthttp.RequestCtx) {
      switch string(ctx.Path()) {
      case "/foo":
      case "/bar":
      case "/baz":
          ctx.Error("not found", fasthttp.StatusNotFound)
    fasthttp.ListenAndServe(":80", m)
  • net/http -> fasthttp conversion table:

    • All the pseudocode below assumes w, r and ctx have these types:
      var (
          w http.ResponseWriter
          r *http.Request
          ctx *fasthttp.RequestCtx
  • VERY IMPORTANT! Fasthttp disallows holding references to RequestCtx or to its' members after returning from RequestHandler. Otherwise data races are inevitable. Carefully inspect all the net/http request handlers converted to fasthttp whether they retain references to RequestCtx or to its' members after returning. RequestCtx provides the following band aids for this case:

    • Wrap RequestHandler into TimeoutHandler.
    • Call TimeoutError before returning from RequestHandler if there are references to RequestCtx or to its' members. See the example for more details.

Use this brilliant tool - race detector - for detecting and eliminating data races in your program. If you detected data race related to fasthttp in your program, then there is high probability you forgot calling TimeoutError before returning from RequestHandler.

Performance optimization tips for multi-core systems

  • Use reuseport listener.
  • Run a separate server instance per CPU core with GOMAXPROCS=1.
  • Pin each server instance to a separate CPU core using taskset.
  • Ensure the interrupts of multiqueue network card are evenly distributed between CPU cores. See this article for details.
  • Use Go 1.6 as it provides some considerable performance improvements.

Fasthttp best practices

  • Do not allocate objects and []byte buffers - just reuse them as much as possible. Fasthttp API design encourages this.
  • sync.Pool is your best friend.
  • Profile your program in production. go tool pprof --alloc_objects your-program mem.pprof usually gives better insights for optimization opportunities than go tool pprof your-program cpu.pprof.
  • Write tests and benchmarks for hot paths.
  • Avoid conversion between []byte and string, since this may result in memory allocation+copy. Fasthttp API provides functions for both []byte and string - use these functions instead of converting manually between []byte and string. There are some exceptions - see this wiki page for more details.
  • Verify your tests and production code under race detector on a regular basis.
  • Prefer quicktemplate instead of html/template in your webserver.

Tricks with []byte buffers

The following tricks are used by fasthttp. Use them in your code too.

  • Standard Go functions accept nil buffers
var (
    // both buffers are uninitialized
    dst []byte
    src []byte
dst = append(dst, src...)  // is legal if dst is nil and/or src is nil
copy(dst, src)  // is legal if dst is nil and/or src is nil
(string(src) == "")  // is true if src is nil
(len(src) == 0)  // is true if src is nil
src = src[:0]  // works like a charm with nil src

// this for loop doesn't panic if src is nil
for i, ch := range src {
    doSomething(i, ch)

So throw away nil checks for []byte buffers from you code. For example,

srcLen := 0
if src != nil {
    srcLen = len(src)


srcLen := len(src)
  • String may be appended to []byte buffer with append
dst = append(dst, "foobar"...)
  • []byte buffer may be extended to its' capacity.
buf := make([]byte, 100)
a := buf[:10]  // len(a) == 10, cap(a) == 100.
b := a[:100]  // is valid, since cap(a) == 100.
  • All fasthttp functions accept nil []byte buffer
statusCode, body, err := fasthttp.Get(nil, "")
uintBuf := fasthttp.AppendUint(nil, 1234)

Related projects

  • fasthttp-contrib - various useful helpers for projects based on fasthttp.
  • iris - web application framework built on top of fasthttp. Features speed and functionality.
  • fasthttp-routing - fast and powerful routing package for fasthttp servers.
  • fasthttprouter - a high performance fasthttp request router that scales well.
  • lu - a high performance go middleware web framework which is based on fasthttp.
  • websocket - Gorilla-based websocket implementation for fasthttp.


  • Why creating yet another http package instead of optimizing net/http?

    Because net/http API limits many optimization opportunities. For example:

    • net/http Request object lifetime isn't limited by request handler execution time. So the server must create a new request object per each request instead of reusing existing objects like fasthttp does.
    • net/http headers are stored in a map[string][]string. So the server must parse all the headers, convert them from []byte to string and put them into the map before calling user-provided request handler. This all requires unnecessary memory allocations avoided by fasthttp.
    • net/http client API requires creating a new response object per each request.
  • Why fasthttp API is incompatible with net/http?

    Because net/http API limits many optimization opportunities. See the answer above for more details. Also certain net/http API parts are suboptimal for use:

  • Why fasthttp doesn't support HTTP/2.0 and WebSockets?

    There are plans for adding HTTP/2.0 and WebSockets support in the future. In the mean time, third parties may use RequestCtx.Hijack for implementing these goodies. See the first third-party websocket implementation on the top of fasthttp.

  • Are there known net/http advantages comparing to fasthttp?


    • net/http supports HTTP/2.0 starting from go1.6.
    • net/http API is stable, while fasthttp API constantly evolves.
    • net/http handles more HTTP corner cases.
    • net/http should contain less bugs, since it is used and tested by much wider audience.
    • net/http works on Go older than 1.5.
  • Why fasthttp API prefers returning []byte instead of string?

    Because []byte to string conversion isn't free - it requires memory allocation and copy. Feel free wrapping returned []byte result into string() if you prefer working with strings instead of byte slices. But be aware that this has non-zero overhead.

  • Which GO versions are supported by fasthttp?

    Go1.5+. Older versions won't be supported, since their standard package miss useful functions.

  • Please provide real benchmark data and sever information

    See this issue.

  • Are there plans to add request routing to fasthttp?

    There are no plans to add request routing into fasthttp. Use third-party routers and web frameworks with fasthttp support:

    See also this issue for more info.

  • I detected data race in fasthttp!

    Cool! File a bug. But before doing this check the following in your code:

  • I didn't find an answer for my question here

    Try exploring these questions.