Jonatas Pedraza jonatasnona

Benchmarking Nginx with Go

There are a lot of ways to serve a Go HTTP application. The best choices depend on each use case. Currently nginx looks to be the standard web server for every new project even though there are other great web servers as well. However, how much is the overhead of serving a Go application behind an nginx server? Do we need some nginx features (vhosts, load balancing, cache, etc) or can you serve directly from Go? If you need nginx, what is the fastest connection mechanism? This are the kind of questions I'm intended to answer here. The purpose of this benchmark is not to tell that Go is faster or slower than nginx. That would be stupid.

So, these are the different settings we are going to compare:

Go HTTP standalone (as the control group)
Nginx proxy to Go HTTP
Nginx fastcgi to Go TCP FastCGI
Nginx fastcgi to Go Unix Socket FastCGI

a simple git branching model (written in 2013)

This is a very simple git workflow. It (and variants) is in use by many people. I settled on it after using it very effectively at Athena. GitHub does something similar; Zach Holman mentioned it in this talk.

Update: Woah, thanks for all the attention. Didn't expect this simple rant to get popular.

Node.js - npm Cheat Sheet

(Full description and list of commands at - https://npmjs.org/doc/index.html)

List of less common (however useful) NPM commands

Prepand ./bin to your $PATH

Make sure to export your local $PATH and prepand relative ./node_modules/.bin/:

-# delete local tag '12345'
-git tag -d 12345
-# delete remote tag '12345' (eg, GitHub version too)
-git push origin :refs/tags/12345
-# alternative approach
-git push --delete origin tagName
-git tag -d tagName

	# This number should be, at maximum, the number of CPU cores on your system.
	# (since nginx doesn't benefit from more than one worker per CPU.)
	worker_processes 8;


	# Determines how many clients will be served by each worker process.
	# (Max clients = worker_connections * worker_processes)
	# "Max clients" is also limited by the number of socket connections available on the system (~64k)
	# run ss -s and u'll see a timewait param
	# The reason for TIMED_WAIT is to handle the case of packets arriving after the socket is closed.

	#!/bin/bash
	clear

	echo "Please enter your e-mail:"
	read email

	# install google chrome
	sudo apt-get install libcurl3 libnspr4-0d libxss1 -y
	wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
	sudo dpkg -i google-chrome; rm google-chrome

	#!/bin/bash
	#
	# PostgreSQL Backup Script Ver 1.0
	# http://autopgsqlbackup.frozenpc.net
	# Copyright (c) 2005 Aaron Axelsen <[email protected]>
	#
	# This script is based of the AutoMySQLBackup Script Ver 2.2
	# It can be found at http://sourceforge.net/projects/automysqlbackup/
	#
	# The PostgreSQL changes are based on a patch agaisnt AutoMySQLBackup 1.9

	# to generate your dhparam.pem file, run in the terminal
	openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048

	# All credit: http://stackoverflow.com/questions/4006324/how-to-atomically-delete-keys-matching-a-pattern-with-redis
	redis-cli [options] KEYS "prefix:*" \| xargs redis-cli [options] DEL