From c749517cdc3f82055e723c4d3fd148e4ff07de26 Mon Sep 17 00:00:00 2001 From: "Dolf Schimmel (Freeaqingme)" Date: Sat, 30 Jan 2016 15:58:00 +0100 Subject: [PATCH] Readme: Suggest use of Go 1.6 for performance --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 94ade03..96a33d6 100644 --- a/README.md +++ b/README.md @@ -347,6 +347,7 @@ code after switching to fasthttp. * Pin each server instance to a separate CPU core using [taskset](http://linux.die.net/man/1/taskset). * Ensure the interrupts of multiqueue network card are evenly distributed between CPU cores. See [this article](https://blog.cloudflare.com/how-to-achieve-low-latency/) for details. +* Use Go 1.6 as it provides some considerable performance improvements. # Fasthttp best practices @@ -433,7 +434,7 @@ uintBuf := fasthttp.AppendUint(nil, 1234) * 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 unnesessary memory allocations avoided by fasthttp. + This all requires unnecessary memory allocations avoided by fasthttp. * net/http client API requires creating new response object per each request. * *Why fasthttp API is incompatible with net/http?*