From 2ee606c4bfe4b0ea01fca7d3e3ebd17f24cbd4f8 Mon Sep 17 00:00:00 2001 From: guFalcon Date: Thu, 9 Feb 2017 07:52:44 +0100 Subject: [PATCH 1/2] Fixed typo. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9eab56d..ba41eba 100644 --- a/README.md +++ b/README.md @@ -238,7 +238,7 @@ FLAVOR=http node index.js ## Results The `http-proxy` lives up to it's name, it proxies requests and does it quite -fast. But as it's build on top of Node.js it quite heavy on the memory. Just a +fast. But as it's build on top of Node.js it's quite heavy on the memory. Just a simple node process starts with a 12MB of memory. For the 10K requests it took around `70mb` of memory. The overhead was of the HTTP proxy was about 5 seconds if you compare it to control test. The HTTPS test was the slowest of all, but From 44d749650669efca14c79b8d3ace93bb1518d831 Mon Sep 17 00:00:00 2001 From: guFalcon Date: Thu, 9 Feb 2017 07:57:25 +0100 Subject: [PATCH 2/2] Fixed a typo. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ba41eba..2a3a44d 100644 --- a/README.md +++ b/README.md @@ -254,7 +254,7 @@ explained because they are all build in pure C. I had high hopes for Nginx and it did not let me down. It had a peak memory of 10MB and it was really fast. The first time I tested Nginx, it had a horrible performance. Node was even faster in SSL then Nginx, I felt like failure, I -genuinely sucked a configuring Nginx. But after some quick tips from some +genuinely sucked at configuring Nginx. But after some quick tips from some friends it was actually a one line change in the config. I had the wrong `ciphers` configured. After some quick tweaking and a confirmation using `openssl s_client -connect server:ip` it was all good and used `RC4` by default