Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed small typos #17

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Fixed small typos #17

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2ee606c
Fixed typo.
guFalcon Feb 9, 2017
44d7496
Fixed a typo.
guFalcon Feb 9, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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
Expand Down