goldeneggg

Dockerについて調べたのでヅラヅラとまとめ ＋ チートシート

概念とか用語とか、とりあえず押さえとくべきもの

• lxc
  • LXC - Wikipedia
  • OSレベル の仮想化ソフトウェア
    • 完全仮想化（ハードウェアをエミュレート、オーバーヘッド大） - KVM etc
    • 準仮想化（ゲストOSがホストOSのAPIを使用、オーバーヘッド中） - Xen, Hyper-V etc。Virtualboxもこちらか
• 仮想機械ではなく、個別のプロセスとネットワークスペースを作り出す仮想環境

hgfischer

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