RobinShen Springshen

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

CentOS7 に PHP5.6 インストール

PHP5.6 インストール

$ sudo su

// 2016.07.16現在 epel-release-7-7
# rpm -Uvh http://ftp.iij.ad.jp/pub/linux/fedora/epel/7/x86_64/e/epel-release-7-7.noarch.rpm

	//查找指定元素的索引
	function arrIndex(val,arr){
	for (var i = 0; i < arr.length; i++) {
	if (arr[i] == val) return i;
	}
	return -1;
	}
	//删除索引元素
	function removeCurEle(val,arr){
	var index = arrIndex(val,arr);

	<?php

	$password = "silic";//设置密码

	error_reporting(E_ERROR);
	header("content-Type: text/html; charset=gb2312");
	set_time_limit(0);

	function Root_GP(&$array)
	{

 <!DOCTYPE html>
 <html lang="en">
   <head>
     <meta charset="utf-8">
     <script src="https://cdn.bootcss.com/jquery/3.3.1/jquery.js"></script>
   </head>
   <body>
 <div class="nav-bj" id="nav-bj">
              <div class="nav" id="nav">
                  <ul style="width:1000px; margin:0 auto;">

	filetype on " 侦测文件类型
	syntax on " 语法高亮
	set autowrite " 自动保存
	set nocompatible " 关闭vi兼容模式
	set showmatch " 高亮显示匹配的括号
	set cursorline " 突出显示当前行
	set number " 显示行号
	set history=1000 " 历史记录数
	set ignorecase " 搜索忽略大小写
	set hlsearch " 高亮被搜索的句子

	# sets the proxy cache path location, max size 2g
	proxy_cache_path /data/nginx/cache levels=1:2 keys_zone=STATIC:100m inactive=24h max_size=2g;

	# transfers the `Host` header to the backend
	proxy_set_header Host $host;

	# uses the defined STATIC cache zone
	proxy_cache STATIC;

	# cache 200 10 minutes, 404 1 minute, others status codes not cached

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

	## From a post on the ML, apropos this:
	## http://lowlatencyweb.wordpress.com/2012/03/20/500000-requestssec-modern-http-servers-are-fast.
	## For sysctl.conf

	net.ipv4.tcp_slow_start_after_idle = 0


	echo "2048 64512" > /proc/sys/net/ipv4/ip_local_port_range
	echo "1" > /proc/sys/net/ipv4/tcp_tw_recycle
	echo "1" > /proc/sys/net/ipv4/tcp_tw_reuse

	# Nginx FastCGI Cache: http://seravo.fi/2013/optimizing-web-server-performance-with-nginx-and-php
	# More Caching: https://www.digitalocean.com/community/tutorials/how-to-setup-fastcgi-caching-with-nginx-on-your-vps
	# Apache Bench Mac: http://kevify.com/2013/ab-on-mac/

	fastcgi_cache_path /var/cache/nginx levels=1:2 keys_zone=MYAPP:100m inactive=60m;
	fastcgi_cache_key "$scheme$request_method$host$request_uri";

	server {
	listen 80;